From: Evert Vorster <evorster@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Fwd: btrfsck: checksum verify failed
Date: Sun, 8 Aug 2010 13:20:02 +0000 [thread overview]
Message-ID: <AANLkTimDAR=2GoQfuhcQisMkssya6ACDQ8Jv_gD1fa+Q@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikncVbqe7BJp+PAT3eCzLVgEWo-OzbmADHyARvB@mail.gmail.com>
---------- Forwarded message ----------
=46rom: Evert Vorster <evorster@gmail.com>
Date: Sun, Aug 8, 2010 at 1:18 PM
Subject: btrfsck: checksum verify failed
To: linux-btrfs@vger.kernel.org
Hi there.
I have a btrfs on a raw device. (/dev/sda insted of in a partition,
like /dev/sda1 )
The device in question is a USB hard drive with a 1TB size.
The device worked fine for a week or so, and was mounted and unmounted
quite a few times without trouble.
The last time the device was unmounted it was a normal unmount.
Now, when I try to mount the device, I get the following in dmesg:
usb 2-1: new high speed USB device using ehci_hcd and address 4
scsi6 : usb-storage 2-1:1.0
scsi 6:0:0:0: Direct-Access=A0=A0=A0=A0 Seagate=A0 FreeAgent GoFlex 014=
8 PQ: 0 ANSI: 4
sd 6:0:0:0: Attached scsi generic sg2 type 0
sd 6:0:0:0: [sdb] 1953525167 512-byte logical blocks: (1.00 TB/931 GiB)
sd 6:0:0:0: [sdb] Write Protect is off
sd 6:0:0:0: [sdb] Mode Sense: 1c 00 00 00
sd 6:0:0:0: [sdb] Assuming drive cache: write through
sd 6:0:0:0: [sdb] Assuming drive cache: write through
=A0sdb: unknown partition table
sd 6:0:0:0: [sdb] Assuming drive cache: write through
sd 6:0:0:0: [sdb] Attached SCSI disk
device label TeraByte1 devid 1 transid 5352 /dev/sdb
parent transid verify failed on 986800398336 wanted 5352 found 5355
parent transid verify failed on 986800398336 wanted 5352 found 5355
parent transid verify failed on 986800398336 wanted 5352 found 5355
btrfs: open_ctree failed
Also, if I try to fsck the device, this is the output:
bin@dora:~# btrfsck /dev/sdb
parent transid verify failed on 986800398336 wanted 5352 found 5355
parent transid verify failed on 986800398336 wanted 5352 found 5355
parent transid verify failed on 986800398336 wanted 5352 found 5355
btrfsck: disk-io.c:739: open_ctree_fd: Assertion `!(!tree_root->node)' =
failed.
Aborted
I am using v 0.19 of the btrfs-tools, and kernel version 2.6.34.1
While a little sad that I can't get at my data anymore, I do have
backups of it. I also want to use the device again, but want to stop
anybody else running into the same problem. So, if you have any
requests like maybe a dd of some small part of the filesystem to study
and see what went wrong, and maybe how to fix it, I would be happy to
oblige. However, If I hear nothing for a day or so, I'll wipe the
filesystem and use the device again.
Kind regards,
-Evert Vorster-
--
http://magnatune.com - Music shared the way it should be.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2010-08-08 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikncVbqe7BJp+PAT3eCzLVgEWo-OzbmADHyARvB@mail.gmail.com>
2010-08-08 13:20 ` Evert Vorster [this message]
2010-08-09 3:32 ` btrfsck: checksum verify failed Evert Vorster
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='AANLkTimDAR=2GoQfuhcQisMkssya6ACDQ8Jv_gD1fa+Q@mail.gmail.com' \
--to=evorster@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;
as well as URLs for NNTP newsgroup(s).