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 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
