From: "Ronny H. Kavli" <ronny.kavli@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Inconsistent reports after disk-error.
Date: Mon, 18 Jan 2010 23:59:37 +0100 [thread overview]
Message-ID: <1263855577.6829.26.camel@bollox.stuffit.loc> (raw)
In-Reply-To: <1263854740.6829.20.camel@bollox.stuffit.loc>
Ah. I can reply to myself after checking the logs when I try to mount
with dmesg(1).
Two successive mount-attempts give indeed a consistent result:
[ 3712.163040] device fsid 794be0222f8f0708-ffaf918752666783 devid 1
transid 9044 /dev/mapper/vg3-vbox1
[ 3712.172059] btrfs: dm-7 checksum verify failed on 142837022720 wanted
5D181110 found 5D18D333 level 0
[ 3712.172931] btrfs: dm-7 checksum verify failed on 142837022720 wanted
5D181110 found 5D18D333 level 0
[ 3712.173433] btrfs: dm-7 checksum verify failed on 142837022720 wanted
5D185110 found 5D18D333 level 0
[ 3712.173440] btrfs: failed to read tree root on dm-7
[ 3712.173762] btrfs: open_ctree failed
[ 3714.210952] device fsid 794be0222f8f0708-ffaf918752666783 devid 1
transid 9044 /dev/mapper/vg3-vbox1
[ 3714.220220] btrfs: dm-7 checksum verify failed on 142837022720 wanted
5D181110 found 5D18D333 level 0
[ 3714.220718] btrfs: dm-7 checksum verify failed on 142837022720 wanted
5D181110 found 5D18D333 level 0
[ 3714.221217] btrfs: dm-7 checksum verify failed on 142837022720 wanted
5D185110 found 5D18D333 level 0
[ 3714.221224] btrfs: failed to read tree root on dm-7
[ 3714.221461] btrfs: open_ctree failed
I then make the the assumption that my copy of btrfsck is not giving
correct output.
-- RHK
next prev parent reply other threads:[~2010-01-18 22:59 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 [this message]
2010-01-20 21:35 ` Chris Mason
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=1263855577.6829.26.camel@bollox.stuffit.loc \
--to=ronny.kavli@gmail.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