From: Stephane CHAZELAS <stephane_chazelas@yahoo.fr>
To: linux-btrfs@vger.kernel.org
Subject: Re: Unable to mount (or, why not to work late at night).
Date: Fri, 28 Oct 2011 11:57:47 +0000 (UTC) [thread overview]
Message-ID: <slrnjal65r.86j.stephane.chazelas@spam.is.invalid> (raw)
In-Reply-To: CAG1y0sfBkczDLRgq=c42_nKwtG3M2UTRB2NHjnZz3L1-jta90w@mail.gmail.com
2011-10-28, 07:57(+07), Fajar A. Nugraha:
[...]
>> Already got 'em. =C2=A0Everything that tries to even think about mod=
ifying stuff
>> (btrfs-zero-log, btrfsck, and btrfs-debug-tree) all dump core:
>
> Your last resort (for now, anyway) might be using "restore" from
> Josef's btrfs-progs: https://github.com/josefbacik/btrfs-progs
>
> It might be able to copy some data.
I also have got one FS in that same situation. I tried
everything on it including that "restore" (which bailed out with
those same error messages IIRC).
The only thing that got me a bit further was to use an alternate
superblock, though that screwed the FS even further as I need to
reboot the machine after trying to mount it (mount hangs and
there are some btrfs tasks using all the CPU time).
=46ortunately, for that one, I had a not too old backup at the
block device level.
--=20
Stephane
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-10-28 11:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 0:32 Unable to mount (or, why not to work late at night) Ken D'Ambrosio
2011-10-28 0:49 ` dima
2011-10-28 0:57 ` Fajar A. Nugraha
2011-10-28 11:57 ` Stephane CHAZELAS [this message]
2011-11-01 15:06 ` Dave
-- strict thread matches above, loose matches on Subject: below --
2011-10-27 15:22 Ken D'Ambrosio
2011-10-27 16:47 ` Helmut Hullen
2011-10-27 22:32 ` Fajar A. Nugraha
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=slrnjal65r.86j.stephane.chazelas@spam.is.invalid \
--to=stephane_chazelas@yahoo.fr \
--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