From: Hugo Mills <hugo@carfax.org.uk>
To: email@joachim-neu.de
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Unable to mount btrfs partition
Date: Fri, 28 Oct 2011 22:09:47 +0100 [thread overview]
Message-ID: <20111028210947.GM29548@carfax.org.uk> (raw)
In-Reply-To: <4941f692b926ed2b19ccde5c3a791cdf@joachim-neu.de>
[-- Attachment #1: Type: text/plain, Size: 2311 bytes --]
On Fri, Oct 28, 2011 at 08:36:28PM +0000, email@joachim-neu.de wrote:
> Today I downgraded from Ubuntu's APT repo "oneiric-proposed" (which
> brings some kernel 3.0.0-13) back to the standard repo "oneiric".
It's odd that switching from one 3.0.0 to another would cause
something bad to happen. Did something else happen in the process,
like a reboot without a clean shutdown? (This includes power loss,
suspend and failure to resume, and Alt-SysRq-b).
> Now I'm not able to mount my btrfs / and /home (both on the same
> partition) anymore:
>
> device fsid SOME-UUID devid 1 transid 84229 /dev/dm-0
> parent transid verify failed on 77078528 wanted 83774 found 84226
> parent transid verify failed on 77078528 wanted 83774 found 84226
> parent transid verify failed on 77078528 wanted 83774 found 84226
> parent transid verify failed on 77078528 wanted 83774 found 84226
> btrfs: open_ctree failed
>
> The boot process drops to the initramfs shell with no btrfsck
> available.
It wouldn't make any difference if it were -- btrfsck doesn't
actually fix anything, I'm afraid. This error message is regrettably
generic, and covers a whole range of evils. It's possible that 3.1 may
be able to deal swith the breakage ufficiently well to allow you to
boot and copy your files.
> I tried to boot with both the "new" 3.0.0-13 kernel and
> the old 3.0.0-12 and 3.0.0-11 kernels -- no success. I'm running a
> live cd right now with 3.0.0-12 and I get the above error no matter
> what I do: no mount, no fsck, no nothing.
>
> I really hope someone can help me get my data back...
You could try using a 3.1 kernel, as I suggested above. Failing
that, in josef's git repository at [1], you will find a tool called
"restore". This should allow you to copy any files that had been
modified since your last backup. If you haven't got backups, you
*really* should look into getting some before continuing to use a
filesystem marked as EXPERIMENTAL...
Hugo.
[1] https://github.com/josefbacik/btrfs-progs
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- If you're not part of the solution, you're part ---
of the precipiate.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2011-10-28 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 20:36 Unable to mount btrfs partition email
2011-10-28 21:09 ` Hugo Mills [this message]
2011-10-28 23:45 ` email
2011-10-31 4:19 ` dima
2011-10-31 8:30 ` Hugo Mills
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=20111028210947.GM29548@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=email@joachim-neu.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