From: Chris Mason <chris.mason@oracle.com>
To: Andrej Podzimek <andrej@podzimek.org>
Cc: Josef Bacik <josef@redhat.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: parent transid verify failures on 2.6.39
Date: Wed, 22 Jun 2011 21:45:20 -0400 [thread overview]
Message-ID: <1308793398-sup-9234@shiny> (raw)
In-Reply-To: <4E026FD4.7020606@podzimek.org>
Excerpts from Andrej Podzimek's message of 2011-06-22 18:42:28 -0400:
>
> Could I try your hack, pretty please? If there's any chance it could either resolve this problem
>
> http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg10683.html ,
>
> or at least restore the data from the filesystem, then I'd like to give it a go. Waiting for the new btrfsck is currently not an option for me :-)
It looks like your box is failing to read the extent allocation tree.
We don't allow the mount to proceed without that tree, but you don't
actually need it for a readonly mount (to copy things off).
Josef, is your hack just a mount option to make -o readonly skip the
extent allocation tree?
I can put this into my -o recovery patch and we can give it a try.
-chris
next prev parent reply other threads:[~2011-06-23 1:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 22:42 parent transid verify failures on 2.6.39 Andrej Podzimek
2011-06-23 1:45 ` Chris Mason [this message]
2011-06-23 18:26 ` Daniel Witzel
2011-06-23 19:54 ` Josef Bacik
2011-06-23 21:11 ` Daniel Witzel
2011-06-23 21:35 ` Josef Bacik
2011-06-24 15:46 ` Daniel Witzel
2011-06-24 1:30 ` Andrej Podzimek
2011-06-28 15:46 ` Daniel Witzel
2011-06-28 16:44 ` Mitch Harder
2011-06-28 17:04 ` Daniel Witzel
2011-06-28 17:31 ` Daniel Witzel
-- strict thread matches above, loose matches on Subject: below --
2011-05-25 19:06 Craig Johnson
2011-05-25 19:28 ` Josef Bacik
2011-05-25 19:32 ` Craig Johnson
2011-07-03 7:09 ` Skylar
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=1308793398-sup-9234@shiny \
--to=chris.mason@oracle.com \
--cc=andrej@podzimek.org \
--cc=josef@redhat.com \
--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 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.