From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs raid1 and btrfs raid10 arrays NOT REDUNDANT
Date: Sat, 4 Jan 2014 13:03:11 +0000 (UTC) [thread overview]
Message-ID: <pan$2efb3$5b939250$4914dbcd$c2014fcc@cox.net> (raw)
In-Reply-To: 1511915.CullaLvumH@quad
Chris Samuel posted on Sat, 04 Jan 2014 22:20:20 +1100 as excerpted:
> On Sat, 4 Jan 2014 06:10:14 AM Duncan wrote:
>
>> Btrfs remains under development and there are clear warnings about
>> using it without backups one hasn't tested recovery from or are not
>> otherwise prepared to actually use. It's stated in multiple locations
>> on the wiki; it's stated on the kernel btrfs config option, and it's
>> stated in mkfs.btrfs output when you create the filesystem.
>
> Actually the scary warnings are gone from the Kconfig file for what will
> be the 3.13 kernel. Removed by this commit:
>
> commit 4204617d142c0887e45fda2562cb5c58097b918e
FWIW, I'd characterize that as toned down somewhat, not /gone/. You
don't see ext4 or other "mature" filesystems saying "The filesystem disk
format is no longer unstable, and it's not expected to change
unless" ..., do you?
"Not expected to change" and etc is definitely toned down from what it
was, no argument there, but it still isn't exactly what one would expect
in a description from a stable filesystem. If there's still some chance
of the disk format changing, what does that say about the code /dealing/
with that disk format? That doesn't sound exactly like something I'd be
comfortable staking my reputation as a sysadmin on as judged fully
reliable and ready for my mission-critical data, for sure!
Tho agreed, one certainly has to read between the lines a bit more for
the kernel option now than they did.
But the real kicker for me was when I redid several of my btrfs
partitions to take advantage of newer features, 16 KiB nodes, etc, and
saw the warning it's giving, yes, in btrfs-progs 3.12 after all the
recent documentation changes, etc. Not everybody builds their own
kernel, but it's kind of hard to get a btrfs filesystem without making
one! (Yes, I know the installers make the filesystem for many people,
and may well hide the output, but if so and the distros don't provide a
similar warning when people choose btrfs, that's entirely on the distros
at that point. Not much btrfs as upstream can do about that.)
--
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:[~2014-01-04 13:03 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 22:28 btrfs raid1 and btrfs raid10 arrays NOT REDUNDANT Jim Salter
2014-01-03 22:42 ` Emil Karlson
2014-01-03 22:43 ` Joshua Schüler
2014-01-03 22:56 ` Jim Salter
2014-01-03 23:04 ` Hugo Mills
2014-01-03 23:04 ` Joshua Schüler
2014-01-03 23:13 ` Jim Salter
2014-01-03 23:18 ` Hugo Mills
2014-01-03 23:25 ` Jim Salter
2014-01-03 23:32 ` Chris Murphy
2014-01-03 23:22 ` Chris Murphy
2014-01-04 6:10 ` Duncan
2014-01-04 11:20 ` Chris Samuel
2014-01-04 13:03 ` Duncan [this message]
2014-01-04 14:51 ` Chris Mason
2014-01-04 15:23 ` Goffredo Baroncelli
2014-01-04 20:08 ` Duncan
2014-01-04 21:22 ` Jim Salter
2014-01-05 11:01 ` Duncan
2014-01-03 23:19 ` Chris Murphy
[not found] ` <CAOjFWZ7zC3=4oH6=SBZA+PhZMrSK1KjxoRN6L2vqd=GTBKKTQA@mail.gmail.com>
2014-01-03 23:42 ` Jim Salter
2014-01-03 23:45 ` Jim Salter
2014-01-04 0:27 ` Chris Murphy
2014-01-04 2:59 ` Jim Salter
2014-01-04 5:57 ` Dave
2014-01-04 11:28 ` Chris Samuel
2014-01-04 14:56 ` Chris Mason
2014-01-05 9:20 ` Chris Samuel
2014-01-05 11:16 ` Duncan
2014-01-04 19:18 ` Chris Murphy
2014-01-04 21:16 ` Jim Salter
2014-01-05 20:25 ` Chris Murphy
2014-01-06 10:20 ` Chris Samuel
2014-01-06 18:30 ` Chris Murphy
2014-01-06 19:25 ` Jim Salter
2014-01-06 22:05 ` Chris Murphy
2014-01-06 22:24 ` Jim Salter
2014-01-07 5:43 ` Chris Samuel
2014-01-06 19:31 ` correct way to rollback a root filesystem? Jim Salter
2014-01-07 11:55 ` Sander
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$2efb3$5b939250$4914dbcd$c2014fcc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.