From: Chris Mason <chris.mason@oracle.com>
To: "Ronny H. Kavli" <ronny.kavli@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Inconsistent reports after disk-error.
Date: Wed, 20 Jan 2010 16:35:55 -0500 [thread overview]
Message-ID: <20100120213555.GH3001@think> (raw)
In-Reply-To: <1263854740.6829.20.camel@bollox.stuffit.loc>
On Mon, Jan 18, 2010 at 11:45:40PM +0100, Ronny H. Kavli wrote:
> I've been running btrfs on some disks with Ubuntu kernel 2.6.31 for a
> while now. Recently I had a bad USB-cable to one of those disks which
> left the btrfs filesystem in a somewhat sad state. Fair enough.
>
> What worries me is what btrfsck reports back to me during two successive
> runs:
> root@bollox:/home/kavli# btrfsck /dev/mapper/vg3-vbox1
> checksum verify failed on 142837022720 wanted 5D18D333 found 95085E8
> checksum verify failed on 142837022720 wanted 5D18D333 found 95085E8
> checksum verify failed on 142837022720 wanted 5D18D333 found 95085E8
> btrfsck: disk-io.c:741: open_ctree_fd: Assertion `!(!tree_root->node)'
> failed.
> Aborted
> root@bollox:/home/kavli# btrfsck /dev/mapper/vg3-vbox1
> checksum verify failed on 142837022720 wanted 5D18D333 found 81D15E8
> checksum verify failed on 142837022720 wanted 5D18D333 found 81D15E8
> checksum verify failed on 142837022720 wanted 5D18D333 found 81D15E8
> btrfsck: disk-io.c:741: open_ctree_fd: Assertion `!(!tree_root->node)'
> failed.
> Aborted
>
> I'd expected the checksums for the two separate runs to be equal.
>
> This is a vanilla filesystem that resides on one physical disk:
> root@bollox:/home/kavli# btrfs-show /dev/mapper/vg3-vbox1
> failed to read /dev/sr0
> Label: none uuid: 08078f2f-22e0-4b79-8367-66528791afff
> Total devices 1 FS bytes used 106.79GB
> devid 1 size 232.88GB used 218.04GB
> path /dev/mapper/vg3-vbox1
>
> Btrfs Btrfs v0.19
>
> I've googled a bit and found one case with a similar problem in a raid1
> setup (I guess incorrectly stated as raid0):
> http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg03429.html
>
> There were no followups beyond that point which stated the cause of this
> behaviour.
I haven't been able to reproduce it locally, but I definitely think it
sounds like the same problem. Have you tried the btrfs-map-logical
program in the unstable btrfs-progs repo?
-chris
next prev parent reply other threads:[~2010-01-20 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 22:45 Inconsistent reports after disk-error Ronny H. Kavli
2010-01-18 22:59 ` Ronny H. Kavli
2010-01-20 21:35 ` Chris Mason [this message]
2010-01-20 21:36 ` 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=20100120213555.GH3001@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=ronny.kavli@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.