From: "A. James Lewis" <james@fsck.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: Recover Corruption - verify_parent_transid
Date: Tue, 10 Aug 2010 05:37:41 +0100 [thread overview]
Message-ID: <1281415061.3192.23.camel@hardline> (raw)
Not being one of the developers on this project, I cannot offer you a
solution to recovering data from this volume, and my guess is that a
ready solution is unlikely to be forthcoming simply because if this was
possible then btrfsck would include the code to recover the filesystem
already.
However, rather than simply observe that anything not backed up is
lost... I thought I would offer the solution of the 4th dimension....
The data is not "lost", but simply unavailable to you until the tools to
repair the filesystem have been developed further. If I had something
critical which had become inaccessible, I might be tempted to put the
drive on a shelf for 6 months and see if btrfsck was able to repair
filesystems by then. It may be that the on disk format is changed
before that happens, but I understand that this is now relatively
unlikely.
A. James Lewis
next reply other threads:[~2010-08-10 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 4:37 A. James Lewis [this message]
2010-08-10 10:30 ` Recover Corruption - verify_parent_transid Daniel Kozlowski
[not found] <AANLkTi=ni92UexMf1xB7ODY3R0Om3K9LmaA_4967knRL@mail.gmail.com>
2010-08-10 2:43 ` Jason Switzer
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=1281415061.3192.23.camel@hardline \
--to=james@fsck.co.uk \
--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).