From: Arne Jansen <sensille@gmx.net>
To: Erik Jensen <eriksjunk@rkjnsn.net>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Recovering data from old corrupted file system
Date: Tue, 22 Nov 2011 09:23:55 +0100 [thread overview]
Message-ID: <4ECB5C1B.5000505@gmx.net> (raw)
In-Reply-To: <CAGh96GFUS-1X-o8n+N_fCRc=6nViru+tM9obJMgSYuLf7D-MpQ@mail.gmail.com>
On 22.11.2011 04:19, Erik Jensen wrote:
> I have a corrupted multi-device file system that got corrupted ages
> ago (as I recall, one of the drives stopped responding, causing btrfs
> to panic). I am hoping to recover some of the data. For what it's
> worth, here is the dmesg output from trying to mount the file system
> on a 3.0 kernel:
>
> device label Media devid 6 transid 816153 /dev/sdq
> device label Media devid 7 transid 816153 /dev/sdl
> device label Media devid 11 transid 816153 /dev/sdj
> device label Media devid 9 transid 816153 /dev/sdk
> device label Media devid 10 transid 816153 /dev/sdi
> device label Media devid 3 transid 816152 /dev/sdh
> device label Media devid 4 transid 816152 /dev/sdf
> device label Media devid 1 transid 816152 /dev/sdg
> device label Media devid 2 transid 816152 /dev/sde
> device label Media devid 8 transid 816153 /dev/sdb
> parent transid verify failed on 47051597279232 wanted 816153 found 816151
> parent transid verify failed on 47051597279232 wanted 816153 found 816151
> parent transid verify failed on 47051597279232 wanted 816153 found 816151
>
> Most of the data is unimportant at this point, and I don't have enough
> extra space elsewhere to store it all anyway. Is there any way I could
> get a read-only view of the file system to pull off the bits I need?
There are some patches in preparation that should help you
recover from this situation. The solution is to mount with
a superblock of generation 816152, but the current set of
tools won't allow for that.
>
> Any help would be greatly appreciated.
>
> Thanks.
>
> -- Erik Jensen
> --
> 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
prev parent reply other threads:[~2011-11-22 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 3:19 Recovering data from old corrupted file system Erik Jensen
2011-11-22 8:23 ` Arne Jansen [this message]
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=4ECB5C1B.5000505@gmx.net \
--to=sensille@gmx.net \
--cc=eriksjunk@rkjnsn.net \
--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).