From: "Ryan C. Underwood" <nemesis-lists@icequake.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Several unhappy btrfs's after RAID meltdown
Date: Sun, 12 Feb 2012 10:31:34 -0600 [thread overview]
Message-ID: <20120212163134.GA15216@localhost.localdomain> (raw)
In-Reply-To: <20120207174907.GF5639@localhost.localdomain>
So, I examined the below filesystem, the one of the two that I would
really like to restore. There is basically nothing but zeros, and
very occasionally a sparse string of data, until exactly 0x200000
offset, at which point the data is suddenly very packed and looks like
usual compressed data should. Is there a way one could de-LZO the
data chunkwise and dump to another device so I could even get an idea
what I am looking at? What about a 'superblock' signature I can scan
for?
> # /usr/local/btrfs-progs/bin/restore -v /dev/mapper/tr5ut-vicep--library /mnt2
> 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
> restore: root-tree.c:46: btrfs_find_last_root: Assertion
> `!(path->slots[0] == 0)' failed.
> Aborted
--
Ryan C. Underwood, <nemesis@icequake.net>
next prev parent reply other threads:[~2012-02-12 16:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 18:41 Several unhappy btrfs's after RAID meltdown Ryan C. Underwood
2012-02-07 3:39 ` 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 [this message]
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=20120212163134.GA15216@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).