From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hard drive storage questions
Date: Tue, 5 May 2015 06:56:20 -0400 [thread overview]
Message-ID: <CAGfcS_khWSEaKFXD_eADjgDDkLxzpHN+HEswE69Liez0Zbu7Ug@mail.gmail.com> (raw)
In-Reply-To: <CADqA9ub7e1dLVoq+oVUff-twj7B4ws4sOnotyxH3SGBVvY1tcw@mail.gmail.com>
On Mon, May 4, 2015 at 2:42 PM, Nuno Magalhães <nunomagalhaes@eu.ipp.pt> wrote:
>
> Another approach is ZFS with RAID-Z or similar. I don't know how/if
> ZFS splits data among the drives, but i assume it's wise enough to do
> so in a way similar to a RAID+LVM combo.
>...
>
> I don't know about btrfs, seems like it's still in a testing-phase so
> i'm not touching it yet.
My understanding is that both zfs and btrfs on linux are fairly
experimental. The codebase for zfs is much more mature in general,
though its integration on Linux is recent. The codebase for btrfs
changes rapidly, with quite a few regressions. I've never
irrecoverably lost data on btrfs, but it wouldn't be my first choice
for a production environment unless I basically did my own QC on the
kernel. However, all my important data is on btrfs nonetheless (with
a full backup to ext4 daily right now).
--
Rich
next prev parent reply other threads:[~2015-05-05 10:56 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 8:39 [gentoo-user] Hard drive storage questions Dale
2015-04-28 14:49 ` Francisco Ares
2015-04-28 15:01 ` Alan McKinnon
2015-04-28 15:24 ` Neil Bothwick
2015-04-28 17:38 ` Rich Freeman
2015-04-28 18:11 ` Neil Bothwick
2015-04-28 18:31 ` Rich Freeman
2015-04-28 18:41 ` Neil Bothwick
2015-04-28 22:02 ` [gentoo-user] " walt
2015-04-29 1:24 ` Rich Freeman
2015-04-29 6:20 ` Alan McKinnon
2015-04-29 14:31 ` Grant Edwards
2015-04-29 6:13 ` [gentoo-user] " Alan McKinnon
2015-04-29 7:52 ` Neil Bothwick
2015-05-04 7:39 ` Dale
2015-05-04 7:46 ` Neil Bothwick
2015-05-04 8:13 ` Mick
2015-05-04 8:26 ` Dale
2015-05-04 8:23 ` Dale
2015-05-04 10:31 ` Neil Bothwick
2015-05-04 10:40 ` Dale
2015-05-04 11:26 ` Neil Bothwick
2015-05-09 10:56 ` Dale
2015-05-09 12:59 ` Rich Freeman
2015-05-09 14:46 ` Todd Goodman
2015-05-09 18:16 ` Rich Freeman
2015-05-04 11:35 ` Rich Freeman
2015-05-04 18:42 ` Nuno Magalhães
2015-05-05 6:41 ` Alan McKinnon
2015-05-05 10:56 ` Rich Freeman [this message]
2015-05-05 11:33 ` Neil Bothwick
2015-05-05 12:05 ` Mick
2015-05-05 12:21 ` Neil Bothwick
2015-05-05 12:39 ` Mick
2015-05-05 12:53 ` Rich Freeman
2015-05-05 21:50 ` Neil Bothwick
2015-05-05 22:21 ` Bill Kenworthy
2015-05-05 22:33 ` Bill Kenworthy
2015-05-04 10:57 ` Alan Mackenzie
2015-04-28 15:02 ` Rich Freeman
2015-05-04 7:23 ` Dale
2015-05-05 3:01 ` Walter Dnes
-- strict thread matches above, loose matches on Subject: below --
2018-11-09 1:16 Dale
2018-11-09 1:31 ` Jack
2018-11-09 1:43 ` Dale
2018-11-09 2:04 ` Andrew Lowe
2018-11-09 2:07 ` Bill Kenworthy
2018-11-09 8:39 ` Neil Bothwick
2018-11-09 2:29 ` Rich Freeman
2018-11-09 8:17 ` Bill Kenworthy
2018-11-09 13:25 ` Rich Freeman
2018-11-09 9:02 ` J. Roeleveld
2018-11-11 0:45 ` Dale
2018-11-11 21:41 ` Wol's lists
2018-11-11 22:17 ` Dale
2018-11-09 9:24 ` Wols Lists
2015-04-27 7:41 Dale
2015-04-28 18:25 ` Daniel Frey
2015-04-28 21:23 ` Dale
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_khWSEaKFXD_eADjgDDkLxzpHN+HEswE69Liez0Zbu7Ug@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