From: "Ken D'Ambrosio" <ken@jots.org>
To: <linux-btrfs@vger.kernel.org>
Subject: Unable to mount (or, why not to work late at night).
Date: Thu, 27 Oct 2011 11:22:52 -0400 [thread overview]
Message-ID: <47bc8413b603ceebfb85404d10cdc5f3@www.jots.org> (raw)
So, I was trying to downgrade my Ubuntu last night, and, before doing anything
risky like that, I backed up my disk via dd to an image on an external disk.
The critical part here is that I'm afraid I did something truly stupid: I'm
afraid I did the dd... live. (I can't swear to this, and it does seem
unlikely, but it also seems to be the most likely circumstance.)
So, I dd'd everything back, and now it crashes on boot. Booting to a 2.6.x
kernel (which is what I had on-hand on a USB drive) mounts it, but doesn't let
me *do* anything (though it spews btrfs errors in dmesg). Getting Ubuntu 11.10
(kernel rev. 3.0.0) gives me this:
[ 121.226246] device fsid d657ce6a-d353-4c2c-858a-6a1f4d9e766e devid 1 transid
217713 /dev/sda1
[ 121.232430] parent transid verify failed on 100695031808 wanted 217713 found
217732
[ 121.232898] parent transid verify failed on 100695031808 wanted 217713 found
217732
[ 121.233357] parent transid verify failed on 100695031808 wanted 217713 found
217732
[ 121.233365] parent transid verify failed on 100695031808 wanted 217713 found
217732
[ 121.248231] btrfs: open_ctree failed
As I have this complete image on-disk, I'm more than willing to try Extreme
Measures(tm), whatever that might entail. If I can't get it back, it's not
like it's the loss of my job or anything, but there *is* stuff I'd really like
to get back.
Thanks,
-Ken
next reply other threads:[~2011-10-27 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-27 15:22 Ken D'Ambrosio [this message]
2011-10-27 16:47 ` Unable to mount (or, why not to work late at night) Helmut Hullen
2011-10-27 22:32 ` Fajar A. Nugraha
-- strict thread matches above, loose matches on Subject: below --
2011-10-28 0:32 Ken D'Ambrosio
2011-10-28 0:49 ` dima
2011-10-28 0:57 ` Fajar A. Nugraha
2011-10-28 11:57 ` Stephane CHAZELAS
2011-11-01 15:06 ` Dave
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=47bc8413b603ceebfb85404d10cdc5f3@www.jots.org \
--to=ken@jots.org \
--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