public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Safeguarding strategies against SSD data loss
Date: Mon, 27 Oct 2014 11:36:46 -0400	[thread overview]
Message-ID: <CAGfcS_kYd0dVS4Wd3JG=dgacTUVDy+NrPUpuDAGC2WexnOTo=A@mail.gmail.com> (raw)
In-Reply-To: <201410271522.32452.michaelkintzios@gmail.com>

On Mon, Oct 27, 2014 at 11:22 AM, Mick <michaelkintzios@gmail.com> wrote:
>
> Thanks Rich, I have been reading your posts about btrfs with interest, but
> have not yet used it on my systems.  Is btrfs agreeable with SSDs, or should I
> be using f2fs:
>

Btrfs will auto-detect SSDs and optimize itself differently, and is
generally considered to be fine on SSDs.  Of course, btrfs itself is
experimental and may eat your data, especially if you get it too full,
but you'll be no worse off for running it on an SSD.

I doubt you'll find any general-purpose filesystem that works as well
overall on an SSD as something like f2fs as this is log-based and
designed with SSDs in mind.  However, f2fs is also very immature and
also carries risks, and the last time I checked it was missing some
features like xattrs as well.  It also doesn't have anything like
btrfs send to serialize your data.

zfs on linux might be another option.  I don't know how well it
handles SSDs in general, and you have to fuss with FUSE and a boot
partition as I don't think grub supports it - it could be a bit of a
PITA for a single-drive system.  However, it is probably more mature
than btrfs overall, and it certainly supports send.

I just had a btrfs near-miss which caused me to rethink how I'm
managing my own storage.  I was half-tempted to blog on it - it is a
bit frustrating as I believe we're right in the middle of the shift
between the traditional filesystems and the next-generation ones.
Sticking with the old means giving up a lot of potential benefits, but
there are a lot of issues with jumping ship as well as the new systems
all lack maturity or are not feature-complete yet.  I was looking at
f2fs, btrfs, and zfs again this weekend and the issues I struggle with
are the immaturity of btrfs and f2fs, the lack of working parity raid
on btrfs, the lack of many features on f2fs, and the inability to
resize vdevs on zfs which means on a system with few drives you get
locked in.  I suspect all of those will change in time, but not yet!

--
Rich


  reply	other threads:[~2014-10-27 15:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-27  9:24 [gentoo-user] Safeguarding strategies against SSD data loss Mick
2014-10-27 10:30 ` Alec Ten Harmsel
2014-10-27 11:11 ` Alan McKinnon
2014-10-27 13:13   ` Rich Freeman
2014-10-27 15:15     ` [gentoo-user] " James
2014-10-27 15:23       ` Mick
2014-10-27 15:22     ` [gentoo-user] " Mick
2014-10-27 15:36       ` Rich Freeman [this message]
2014-10-27 16:52         ` Pandu Poluan
2014-10-27 17:26           ` Volker Armin Hemmann
2014-10-27 17:30           ` Rich Freeman
2014-10-28  0:41             ` Pandu Poluan
2014-10-28  1:13               ` Rich Freeman
2014-10-28  3:45           ` Tom H
2014-10-27 17:23         ` Volker Armin Hemmann
2014-10-27 17:37           ` Rich Freeman
2014-10-28  0:56             ` Pandu Poluan
2014-10-28  3:49             ` Tom H
2014-10-27 17:20       ` Volker Armin Hemmann
2014-10-27 17:17     ` Volker Armin Hemmann
2014-10-27 12:27 ` Philip Webb
2014-10-27 14:12   ` [gentoo-user] Safeguarding strategies against SSD data loss : PS Philip Webb
2014-10-27 15:16   ` [gentoo-user] Safeguarding strategies against SSD data loss Mick

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_kYd0dVS4Wd3JG=dgacTUVDy+NrPUpuDAGC2WexnOTo=A@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