From: Chris Mason <chris.mason@oracle.com>
To: Tommy Jonsson <quazzie@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Fsck, parent transid verify failed
Date: Thu, 02 Dec 2010 11:21:23 -0500 [thread overview]
Message-ID: <1291306826-sup-7837@think> (raw)
In-Reply-To: <003501cb9147$09197540$1b4c5fc0$@gmail.com>
Excerpts from Tommy Jonsson's message of 2010-12-01 06:00:56 -0500:
> Hi folks!
>
> Been using btrfs for quite a while now, worked great until now.
> Got power-loss on my machine and now i have the "parent transid verify
> failed on X wanted X found X" problem.
> So I can't get it to mount.
>
> My btrfs is spread over sda (2tb), sdc(2tb), sdd(1tb).
>
> Is this something that an offline fsck could fix ?
> If so is the fsck-util being developed ?
> Is there a way to mount the FS in a read-only mode or something to rescue
> the data ?
Which kernel are you on? Unless you formatted with -m raid0, the
current git tree should be able to read this FS by using the second copy
of the metadata.
-chris
next prev parent reply other threads:[~2010-12-02 16:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 11:00 Fsck, parent transid verify failed Tommy Jonsson
2010-12-02 16:21 ` Chris Mason [this message]
2010-12-02 21:49 ` Tommy Jonsson
[not found] ` <AANLkTim5-5KQ3_sEb9WY+O1Uj36=3M3i_yQKeuSb7Qe5@mail.gmail.com>
2010-12-02 21:50 ` Chris Mason
2010-12-02 21:59 ` Tommy Jonsson
2010-12-02 22:16 ` Tommy Jonsson
2010-12-08 20:07 ` Tommy Jonsson
2010-12-09 17:14 ` Chris Mason
2010-12-15 12:39 ` Tommy Jonsson
2011-01-03 15:27 ` Tommy Jonsson
2010-12-09 16:21 ` Tom Kuther
2010-12-10 20:11 ` Chris Mason
2010-12-12 11:21 ` Tom Kuther
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=1291306826-sup-7837@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quazzie@gmail.com \
/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).