From: Alexandre Oliva <oliva@gnu.org>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs raid5
Date: Sat, 26 Oct 2013 05:21:17 -0200 [thread overview]
Message-ID: <orob6c7b0y.fsf@livre.home> (raw)
In-Reply-To: <pan$8e391$f46eecbc$498ef5f9$8d48b882@cox.net> (Duncan's message of "Wed, 23 Oct 2013 00:50:51 +0000 (UTC)")
On Oct 22, 2013, Duncan <1i5t5.duncan@cox.net> wrote:
> the quick failure should they try raid56 in its current state simply
> alerts them to the problem they already had.
What quick failure? There's no such thing in place AFAIK. It seems to
do all the work properly, the limitations in the current implementation
will only show up when an I/O error kicks in. I can't see any
indication, in existing announcements, that recovery from I/O errors in
raid56 is missing, let alone that it's so utterly and completely broken
that it will freeze the entire filesystem and require a forced reboot to
unmount the filesystem and make any other data in it accessible again.
That's far, far worse than the general state of btrfs, and that's not a
documented limitation of raid56, so how would someone be expected to
know about it? It certainly isn't obvious by having a cursory look at
the code either.
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist Red Hat Brazil Compiler Engineer
next prev parent reply other threads:[~2013-10-26 7:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 15:45 btrfs raid5 lilofile
2013-10-22 13:27 ` Duncan
2013-10-22 16:00 ` David Sterba
2013-10-22 17:18 ` Alexandre Oliva
2013-10-22 17:40 ` Brendan Hide
2013-10-22 19:24 ` Alexandre Oliva
2013-10-23 0:50 ` Duncan
2013-10-26 7:21 ` Alexandre Oliva [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-22 2:30 shuo lv
2013-10-22 13:30 ` Duncan
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=orob6c7b0y.fsf@livre.home \
--to=oliva@gnu.org \
--cc=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).