From: Daniel J Blueman <daniel@quora.org>
To: Linux BTRFS <linux-btrfs@vger.kernel.org>
Cc: Chris Mason <chris.mason@oracle.com>
Subject: 'bad tree block start' mount failure...
Date: Tue, 20 Mar 2012 23:43:34 +0800 [thread overview]
Message-ID: <CAMVG2suJw2miSP9QUi-ArFrzS0-okN0_MsLPZTc6Xv7xkjLHDw@mail.gmail.com> (raw)
Booting linux 3.3, I found a particular set of steps [1] produces an
fs which is unmountable [2]. This also occurs when data is written
after mounting, so is entirely possible to hit in practice if RAID-0
is used.
Many thanks,
Daniel
--- [1]
mkfs.btrfs -m raid0 -d raid0 /dev/sdb1 /dev/sdc1
mount /dev/sdb1 /mnt
umount /mnt
mount /dev/sdb1 /mnt -o compress
umount /mnt
mount /dev/sdb1 /mnt -o ssd
umount /mnt
mount /dev/sdb1 /mnt -o discard
umount /mnt
mount /dev/sdb1 /mnt
<mount failure>
--- [2]
[13259.593809] btrfs bad tree block start 0 37715968
[13259.593832] btrfs: failed to read tree root on sdc1
[13259.594221] btrfs: open_ctree failed
--
Daniel J Blueman
next reply other threads:[~2012-03-20 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 15:43 Daniel J Blueman [this message]
2012-03-20 16:16 ` 'bad tree block start' mount failure Andrea Gelmini
2012-03-21 10:19 ` Daniel J Blueman
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=CAMVG2suJw2miSP9QUi-ArFrzS0-okN0_MsLPZTc6Xv7xkjLHDw@mail.gmail.com \
--to=daniel@quora.org \
--cc=chris.mason@oracle.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).