linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Pasch <thomas.pasch@gmx.de>
To: linux-btrfs@vger.kernel.org
Subject: corrupt btrfs
Date: Sun, 24 Nov 2013 19:38:26 +0100	[thread overview]
Message-ID: <529247A2.4090905@gmx.de> (raw)

Hello,

yes, I've got it. I know that btrfs is experimental, and I've got a
backup (well, it is a little bit older, but anyway...). I read
[https://btrfs.wiki.kernel.org/index.php/Problem_FAQ] and
[https://btrfs.wiki.kernel.org/index.php/Restore] and have done what it
is suggested there (including the problematic btrfs-zero-log !). In
addition, I run Ubuntu 13.10, that does rule me out from being a
sensible person.

Beside that, I tried btrfs-find-root. It shows something like:

Well block 144572416 seems great, but generation doesn't match,
have=250241, want=250412 level 0
Well block 252919808 seems great, but generation doesn't match,
have=250404, want=250412 level 0
Well block 282722304 seems great, but generation doesn't match,
have=250093, want=250412 level 0
Well block 291414016 seems great, but generation doesn't match,
have=250094, want=250412 level 0
Well block 302501888 seems great, but generation doesn't match,
have=250095, want=250412 level 0
Well block 310611968 seems great, but generation doesn't match,
have=249927, want=250412 level 0
Well block 319311872 seems great, but generation doesn't match,
have=250097, want=250412 level 0
[...]

What I'm missing here is some line starting with 'Generation: ...'.
Well, it is not there...

Certainly, the 'btrfs restore -t n /dev/sda7 /mnt/restore' trick does
not find anything useful.

Is there anything left I could try before giving up on this?

Kind regards,

Thomas


                 reply	other threads:[~2013-11-24 18:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=529247A2.4090905@gmx.de \
    --to=thomas.pasch@gmx.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).