From: "Ryan C. Underwood" <nemesis-lists@icequake.net>
To: linux-btrfs@vger.kernel.org
Subject: Several unhappy btrfs's after RAID meltdown
Date: Sun, 5 Feb 2012 12:41:28 -0600 [thread overview]
Message-ID: <20120205184128.GC18806@localhost.localdomain> (raw)
Hi,
I had a RAID5 double disk failure (40 megs or so bad sectors near
middle of the second failed disk), bad news but I recovered what I was
able to.
The RAID contained a dm-crypt physical volume which then contained
four logical volumes. Two are EXT4 and two BTRFS, about 1TB in size
each.
The failure occurred while the volumes were online and in use, so in
addition to what was unreadable, all pending writes to the device
between the failure and when the problem was discovered were lost as
well.
The two ext4, fortunately, had some relatively minor corruption which
was cleared up with a few rounds of fsck. The two btrfs are
completely unhappy though and I do not know how to proceed, since
btrfs problems are new to me. Any suggestions are welcome.
Here is the basic picture of what is going on.
# cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
#/dev/mapper/tr5ut-media /mnt/media btrfs
defaults,compress=lzo,space_cache 0 2
/dev/mapper/tr5ut-media /mnt/media ext4 defaults 0 2
/dev/mapper/tr5ut-vicep--library /vicepa auto
defaults,compress=lzo,space_cache 0 2
/dev/mapper/tr5ut-vicep--clones /vicepb auto
defaults,compress=lzo,space_cache 0 2
You can see that btrfs device scan does not find anything, while
btrfs-show finds one of the volumes and not the other. Fscking the
found volume halts due to checksum and assertion errors, while fscking
the other volume fails completely, I guess due to a missing
'superblock' type structure?
seraph:~# btrfs device scan
Scanning for Btrfs filesystems
failed to read /dev/sr0
seraph:~# btrfs-show
**
** WARNING: this program is considered deprecated
** Please consider to switch to the btrfs utility
**
failed to read /dev/sr0: No medium found
Label: vicep-library uuid: 89b14d35-b31a-4fbe-a2d9-cb83cbcd3851
Total devices 1 FS bytes used 254.35GB
devid 1 size 1.00TB used 299.04GB path /dev/dm-32
Btrfs Btrfs v0.19
seraph:~# btrfsck /dev/mapper/tr5ut-vicep--library
checksum verify failed on 317874630656 wanted 8E19212D found FFFFFFA6
checksum verify failed on 317874630656 wanted 8E19212D found FFFFFFA6
checksum verify failed on 317874630656 wanted 491D9C1A found FFFFFFA6
checksum verify failed on 317874630656 wanted 8E19212D found FFFFFFA6
Csum didn't match
btrfsck: root-tree.c:46: btrfs_find_last_root: Assertion
`!(path->slots[0] == 0)' failed.
Aborted
seraph:~# btrfsck /dev/mapper/tr5ut-vicep--clones
No valid Btrfs found on /dev/mapper/tr5ut-vicep--clones
seraph:~# dpkg -l btrfs-tools
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Description
+++-=============================================-=============================================-==========================================================================================================
ii btrfs-tools 0.19+20111105-2
Checksumming Copy on Write Filesystem utilities
--
Ryan C. Underwood, <nemesis@icequake.net>
next reply other threads:[~2012-02-05 18:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 18:41 Ryan C. Underwood [this message]
2012-02-07 3:39 ` Several unhappy btrfs's after RAID meltdown Ryan C. Underwood
2012-02-07 4:17 ` Liu Bo
2012-02-07 15:03 ` Ryan C. Underwood
2012-02-07 9:53 ` Duncan
2012-02-07 14:04 ` Ryan C. Underwood
2012-02-07 14:36 ` Mitch Harder
2012-02-07 15:42 ` Ryan C. Underwood
2012-02-07 17:46 ` Ryan C. Underwood
2012-02-07 17:49 ` Ryan C. Underwood
2012-02-12 16:31 ` Ryan C. Underwood
2012-02-13 13:48 ` David Sterba
2012-06-01 14:38 ` Ryan C. Underwood
2012-11-15 16:00 ` Ryan C. Underwood
2012-11-16 8:39 ` Michael Kjörling
2012-02-08 6:32 ` Chris Samuel
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=20120205184128.GC18806@localhost.localdomain \
--to=nemesis-lists@icequake.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=nemesis@icequake.net \
/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).