From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: btrfs raid 5/6
Date: Thu, 7 Dec 2017 10:26:34 -0500 [thread overview]
Message-ID: <CAGfcS_mq=xeKwE1sZdzLaV_n14VwWCV0ZyYu8wAsKgOieRzmbA@mail.gmail.com> (raw)
In-Reply-To: <20171207145327.GA26110@steinmetzger.isa-ilmenau.de>
On Thu, Dec 7, 2017 at 9:53 AM, Frank Steinmetzger <Warp_7@gmx.de> wrote:
>
> I see. I'm always looking for ways to optimise expenses and cut down on
> environmental footprint by keeping stuff around until it really breaks. In
> order to increase capacity, I would have to replace all four drives, whereas
> with a mirror, two would be enough.
>
That is a good point. Though I would note that you can always replace
the raidz2 drives one at a time - you just get zero benefit until
they're all replaced. So, if your space use grows at a rate lower
than the typical hard drive turnover rate that is an option.
>
> When I configured my kernel the other day, I discovered network block
> devices as an option. My PC has a hotswap bay[0]. Problem solved. :) Then I
> can do zpool replace with the drive-to-be-replaced still in the pool, which
> improves resilver read distribution and thus lessens the probability of a
> failure cascade.
>
If you want to get into the network storage space I'd keep an eye on
cephfs. I don't think it is quite to the point where it is a
zfs/btrfs replacement option, but it could get there. I don't think
the checksums are quite end-to-end, but they're getting better.
Overall stability for cephfs itself (as opposed to ceph object
storage) is not as good from what I hear. The biggest issue with it
though is RAM use on the storage nodes. They want 1GB/TB RAM, which
rules out a lot of the cheap ARM-based solutions. Maybe you can get
by with less, but finding ARM systems with even 4GB of RAM is tough,
and even that means only one hard drive per node, which means a lot of
$40+ nodes to go on top of the cost of the drives themselves.
Right now cephfs mainly seems to appeal to the scalability use case.
If you have 10k servers accessing 150TB of storage and you want that
all in one managed well-performing pool that is something cephfs could
probably deliver that almost any other solution can't (and the ones
that can cost WAY more than just one box running zfs on a couple of
RAIDs).
--
Rich
next prev parent reply other threads:[~2017-12-07 15:26 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
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 [this message]
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='CAGfcS_mq=xeKwE1sZdzLaV_n14VwWCV0ZyYu8wAsKgOieRzmbA@mail.gmail.com' \
--to=rich0@gentoo.org \
--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