From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs says no errors, but booting gives lots of errors
Date: Thu, 15 Oct 2015 02:10:15 +0000 (UTC) [thread overview]
Message-ID: <pan$76e30$947a020c$72d4d9dd$c47081a8@cox.net> (raw)
In-Reply-To: 7505.1444566567@ccs.covici.com
covici posted on Sun, 11 Oct 2015 08:29:27 -0400 as excerpted:
> Thanks, in the ext4 world, I have lvm and lots of things using separate
> lvm's. I don't want to go back to partitions, if btrfs is that fragile,
> maybe I should waita while yet. Or, I could use lvm and put btrfs on
> top of that, but it seems strange to me.
Taking the larger picture perspective, I'd suggest that while btrfs
arguably isn't "that fragile" if you're willing to work with it, it most
definitely is of a status I characterize as "stabilizing, but not yet
fully stable or mature", and as such, isn't likely to be the best choice
for people who just want "sufficiently stable that I don't have to mess
with it or worry about it", particularly if they're also the type that
prefer to run "enterprise stable" or "debian stable" grade distros, which
are, to put it mildly, not known for the up-to-dateness of the versions
of various packages they ship. If that's a description of your comfort
zone, then there's a basic incompatibility between your comfort zone and
btrfs' current state, and btrfs probably isn't the right choice for you
at this point.
In which case, ext3/4, reiserfs (my old favorite, which I had very good
experience with even with not so reliable hardware), xfs, or possibly zfs
if you need the features and are willing to put the money into the
hardware it requires for stability, are more mature and arguably
appropriate choices.
I had in mind to say something about the big-picture like that in an
earlier reply, but forgot...
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-10-15 2:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 12:46 btrfs says no errors, but booting gives lots of errors covici
2015-10-10 14:12 ` Holger Hoffstätte
2015-10-10 14:41 ` covici
2015-10-10 15:46 ` Lionel Bouton
2015-10-10 16:10 ` Holger Hoffstätte
2015-10-10 16:55 ` covici
2015-10-10 22:04 ` Lionel Bouton
2015-10-10 23:02 ` covici
2015-10-10 23:08 ` covici
2015-10-11 12:13 ` Duncan
2015-10-11 12:29 ` covici
2015-10-15 2:10 ` Duncan [this message]
2015-10-10 23:21 ` Lionel Bouton
2015-10-10 23:32 ` covici
2015-10-10 23:58 ` Lionel Bouton
2015-10-11 0:28 ` covici
2015-10-10 16:45 ` covici
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='pan$76e30$947a020c$72d4d9dd$c47081a8@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).