From: "lilofile" <lilofile@aliyun.com>
To: <linux-btrfs@vger.kernel.org>
Subject: bug
Date: Thu, 29 Aug 2013 10:34:00 +0800 [thread overview]
Message-ID: <7c55ea3f-bb6d-4e77-8d2f-6368b437ed6a@aliyun.com> (raw)
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:
[ 192.713953] bio: create slab <bio-1> at 1
[ 192.716230] Btrfs loaded
[ 192.717177] device fsid a0dff7ea-9354-43fd-8516-0e17f370991d devid 1 transid 6 /dev/sdb
[ 192.717712] btrfs: disk space caching is enabled
[ 192.720572] btrfs: failed to read the system array on sdb
[ 192.723398] btrfs: open_ctree failed
linux md raid5 have resync , the test seems btrfs raid5 have not resync,how fix the bug?
next reply other threads:[~2013-08-29 2:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 2:34 lilofile [this message]
2013-08-29 2:43 ` bug Liu Bo
2013-08-29 12:25 ` bug David Sterba
-- 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=7c55ea3f-bb6d-4e77-8d2f-6368b437ed6a@aliyun.com \
--to=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).