From: Martin Wilck <mwilck@arcor.de>
To: linux-btrfs@vger.kernel.org
Subject: Lost /home subvolume after btrfs crash
Date: Wed, 16 Apr 2014 15:53:46 +0200 [thread overview]
Message-ID: <534E8B6A.9060209@arcor.de> (raw)
Hello,
I have a broken btrfs file system on a laptop.
Debug material is available here:
https://www.dropbox.com/sh/utv8b3qd0do6a04/zTwGQCrN9x
Most importantly, the /home subvolume is lost. All attempts to recover
data from it (btrfs-restore, mount -o recovery, btrfsck) have failed so
far (/home is simply empty in the btrfs-restore output), although I was
able to recover most of the other subvolumes and the main FS. The btrfs
tools would typically segfault with failed assertions when analyzing the
FS. Grepping through the entire volume shows that (at least parts of)
/home are still available, but they seem to be disconnected from the
main tree somehow, or the meta data is so corrupt that the tools bail
out trying to find files under it. Making matters worse, the important
data was encrypted using ecryptfs, so I need to recover the ciphertext
first and then find a way to recover the plaintext (I do have the
passphrase).
The crash happened with a rather old OpenSUSE 12.2 kernel (3.4.11-2.16).
The user says she was just surfing the web normally when the crash
occured (no screenshot of the original crash, unfortunately). On the
next boot, the btrfs root file system couldn't be mounted any more.
After that I booted an OpenSUSE 12.3 rescue DVD and created the debug
material shown above.
Any hints how to retrieve files from the /home subvolume from this
corrupt file system would be highly appreciated.
Best regards
Martin
next reply other threads:[~2014-04-16 15:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 13:53 Martin Wilck [this message]
2014-04-16 16:19 ` Lost /home subvolume after btrfs crash Chris Murphy
2014-04-23 18:33 ` Martin Wilck
2014-04-24 3:15 ` Chris Murphy
2014-04-27 19:32 ` Martin Wilck
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=534E8B6A.9060209@arcor.de \
--to=mwilck@arcor.de \
--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).