From: "Richard W.M. Jones" <rjones@redhat.com>
To: linux-btrfs@vger.kernel.org
Subject: Anyone seeing lots of "Check tree block failed" and other errors with latest kernel?
Date: Mon, 8 Oct 2012 15:16:42 +0100 [thread overview]
Message-ID: <20121008141642.GC24071@rhmail.home.annexia.org> (raw)
I'm tracking this bug here:
https://bugzilla.redhat.com/show_bug.cgi?id=863978
Since approx. last week I'm seeing lots of failures in btrfs. The
common factor seems to be that the filesystem is created (mkfs.btrfs
/dev/sda1) and then it is immediately used -- eg. mounted or some
btrfs subtool is run on it. There is no pause or sync between the
operations.
Typical errors include:
mkfs.btrfs /dev/sda1
mount -o /dev/sda1 /sysroot/
[ 96.384211] device fsid 962db3c0-4153-450b-9ca7-c9216e81afe3 devid 1 transid 3 /dev/sda1
[ 96.385314] device fsid 962db3c0-4153-450b-9ca7-c9216e81afe3 devid 1 transid 3 /dev/sda1
[ 96.394158] btrfs: disk space caching is enabled
[ 96.428656] btrfs: failed to recover relocation
[ 96.437190] btrfs: open_ctree failed
and:
btrfsck /dev/sda1
Check tree block failed, want=139264, have=0
Check tree block failed, want=139264, have=0
Check tree block failed, want=139264, have=0
read block failed check_tree_block
Couldn't read chunk root
(There are plenty of others, see the above bug link)
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top
next reply other threads:[~2012-10-08 14:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-08 14:16 Richard W.M. Jones [this message]
2012-10-08 14:27 ` Anyone seeing lots of "Check tree block failed" and other errors with latest kernel? Chris Mason
2012-10-08 14:57 ` Richard W.M. Jones
2012-10-08 15:04 ` Chris Mason
2012-10-08 15:15 ` Richard W.M. Jones
2012-10-08 15:18 ` Chris Mason
2012-10-08 16:42 ` David Sterba
2012-10-08 17:01 ` Richard W.M. Jones
2012-10-08 21:22 ` Richard W.M. Jones
2012-10-09 0:00 ` Chris Mason
2012-10-09 7:20 ` Richard W.M. Jones
2012-10-09 7:33 ` Richard W.M. Jones
2012-10-09 9:00 ` David Sterba
2012-10-10 12:38 ` Chris Mason
2012-10-10 19:38 ` Richard W.M. Jones
2012-10-10 19:41 ` Chris Mason
2012-10-10 19:46 ` Richard W.M. Jones
2012-10-11 7:28 ` Richard W.M. Jones
2012-10-11 11:26 ` Chris Mason
2012-10-29 14:52 ` Richard W.M. Jones
2012-10-09 9:16 ` David Sterba
2012-10-09 9:26 ` Richard W.M. Jones
2012-10-10 11:49 ` Richard W.M. Jones
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=20121008141642.GC24071@rhmail.home.annexia.org \
--to=rjones@redhat.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).