public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Richard Bradfield <bradfier@fstab.me>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: btrfs raid 5/6
Date: Thu, 7 Dec 2017 07:54:41 +0000	[thread overview]
Message-ID: <20171207075441.rwzd5qlk7mdm7rtn@carbon> (raw)
In-Reply-To: <CAGfcS_k02c5Dsn1CJfQyNF5URRxYz1GYiAy+P_JoYnKeqdXs0w@mail.gmail.com>

On Wed, Dec 06, 2017 at 06:35:10PM -0500, Rich Freeman wrote:
>On Wed, Dec 6, 2017 at 6:28 PM, Frank Steinmetzger <Warp_7@gmx.de> wrote:
>>
>> I don’t really care about performance. It’s a simple media archive powered
>> by the cheapest Haswell Celeron I could get (with 16 Gigs of ECC RAM though
>> ^^). Sorry if I more or less stole the thread, but this is almost the same
>> topic. I could use a nudge in either direction. My workplace’s storage
>> comprises many 2× mirrors, but I am not a company and I am capped at four
>> bays.
>>
>> So, Do you have any input for me before I fetch the dice?
>>
>
>IMO the cost savings for parity RAID trumps everything unless money
>just isn't a factor.
>
>Now, with ZFS it is frustrating because arrays are relatively
>inflexible when it comes to expansion, though that applies to all
>types of arrays. That is one major advantage of btrfs (and mdadm) over
>zfs.  I hear they're working on that, but in general there are a lot
>of things in zfs that are more static compared to btrfs.
>
>-- 
>Rich
>

When planning for ZFS pools, at least for home use, it's worth thinking
about your usage pattern, and if you'll need to expand the pool before
the lifetime of the drives rolls around.

I incorporated ZFS' expansion inflexibility into my planned
maintenance/servicing budget. I started out with 4x 2TB disks, limited
to those 4 bays as you are, but planned to replace those drives after a
period of 3-4 years.

By the time the first of my drives began to show SMART errors, the price
of a 3TB drive had dropped to what I had paid for the 2TB models, so I
bought another set and did a rolling upgrade, bringing the pool up to
6TB.

I expect I'll do the same thing late next year, I wonder if 4TB will be
the sweet spot, or if I might be able to get something larger.

-- 
Richard


  parent reply	other threads:[~2017-12-07  7:55 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 22:30 [gentoo-user] OT: btrfs raid 5/6 Bill Kenworthy
2017-12-01 15:59 ` J. Roeleveld
2017-12-01 16:58 ` Wols Lists
2017-12-01 17:14   ` Rich Freeman
2017-12-01 17:24     ` Wols Lists
2017-12-06 23:28     ` Frank Steinmetzger
2017-12-06 23:35       ` Rich Freeman
2017-12-07  0:13         ` Frank Steinmetzger
2017-12-07  0:29           ` Rich Freeman
2017-12-07 21:37             ` Frank Steinmetzger
2017-12-07 21:49               ` Wols Lists
2017-12-07 22:35                 ` Frank Steinmetzger
2017-12-07 23:48                   ` Wols Lists
2017-12-09 16:58                     ` J. Roeleveld
2017-12-09 18:28                       ` Wols Lists
2017-12-09 23:36                         ` Rich Freeman
2017-12-10  9:45                           ` Wols Lists
2017-12-10 15:07                             ` Rich Freeman
2017-12-10 21:00                               ` Wols Lists
2017-12-11  1:33                                 ` Rich Freeman
2017-12-11 23:20                 ` Frank Steinmetzger
2017-12-12 10:15                   ` Neil Bothwick
2017-12-12 12:18                     ` Wols Lists
2017-12-12 13:24                       ` Neil Bothwick
2017-12-07  7:54         ` Richard Bradfield [this message]
2017-12-07  9:28           ` Frank Steinmetzger
2017-12-07  9:52             ` Richard Bradfield
2017-12-07 14:53               ` Frank Steinmetzger
2017-12-07 15:26                 ` Rich Freeman
2017-12-07 16:04                   ` Frank Steinmetzger
2017-12-07 23:09                     ` Rich Freeman
2017-12-07 20:02                 ` Wols Lists
2017-12-07 18:35               ` Wols Lists
2017-12-07 20:17                 ` Richard Bradfield
2017-12-07 20:39                   ` Wols Lists

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171207075441.rwzd5qlk7mdm7rtn@carbon \
    --to=bradfier@fstab.me \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox