From: David Sterba <dsterba@suse.cz>
To: lilofile <lilofile@aliyun.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: bug
Date: Thu, 29 Aug 2013 14:25:23 +0200 [thread overview]
Message-ID: <20130829122523.GG23113@twin.jikos.cz> (raw)
In-Reply-To: <7c55ea3f-bb6d-4e77-8d2f-6368b437ed6a@aliyun.com>
On Thu, Aug 29, 2013 at 10:34:00AM +0800, lilofile wrote:
> I made a btrfs on five disks using RAID5 (-d raid5 for mount option).
> When a power failure occurs, I can not remount btrfs after my system
> reboots. Dmesg for remount is presented as following:
Please note that current implementation of raid5/6 is not completely
crash-safe, as was mentioned in the announcement (eg. here
http://lwn.net/Articles/536038/). The mount could fail if the parity of
metadata blocks is corrupted due to crash.
david
next prev parent reply other threads:[~2013-08-29 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 2:34 bug lilofile
2013-08-29 2:43 ` bug Liu Bo
2013-08-29 12:25 ` David Sterba [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-11 15:11 BUG Mark Murawski
2013-06-12 8:38 ` BUG Duncan
2009-07-24 20:28 Bug Steven Pratt
2009-07-24 20:29 ` Bug Chris Mason
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=20130829122523.GG23113@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=lilofile@aliyun.com \
--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).