From: Martin Wilck <mwilck@arcor.de>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Lost /home subvolume after btrfs crash
Date: Wed, 23 Apr 2014 20:33:56 +0200 [thread overview]
Message-ID: <53580794.3050001@arcor.de> (raw)
In-Reply-To: <7C3AD7C7-44A4-45F3-9634-3E92618DCD15@colorremedies.com>
Chris,
> OpenSUSE 12.3 is using kernel 3.7 which is also old for this sort of recovery attempt. Even openSUSE 13.1 is at 3.11.6 which might work in a bind, but if it doesn't, inevitably someone will suggest you use something even newer.
Thanks for your reply, I appreciate it a lot.
> Current stable is 3.14.1, I suggest giving 3.13 or 3.14 a shot at this with -o ro,recovery as a first step and see if it at least mounts.
I will. Note that with 12.3, which was the most recent media I had at
hand at the time, the FS was actually mountable at first (-o
ro,recovery). But there was no /home and later attempts to actually
access data in other subvolumes failed with the messages in my debug
material.
> And an old kernel implies old btrfs-progs too, which is where the code for btrfsck and btrfs restore is contained. So that needs to be at least v 3.12. And hopefully you didn't use --repair with btrfsck yet.
I did, but I made a block-level copy of the device before.
Thanks again
Martin
next prev parent reply other threads:[~2014-04-23 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 13:53 Lost /home subvolume after btrfs crash Martin Wilck
2014-04-16 16:19 ` Chris Murphy
2014-04-23 18:33 ` Martin Wilck [this message]
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=53580794.3050001@arcor.de \
--to=mwilck@arcor.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.