From: Tommy Jonsson <quazzie@gmail.com>
To: chris.mason@oracle.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Fsck, parent transid verify failed
Date: Thu, 2 Dec 2010 22:49:30 +0100 [thread overview]
Message-ID: <AANLkTimuUZM_j-MA0L6rSOOO2TTq=ap8j+=WjCRj6BL8@mail.gmail.com> (raw)
In-Reply-To: <1291306826-sup-7837@think>
I'm on kernel 2.6.35
I can't remember if i used -m raid0.
I think i just used "mkfs.btrfs /dev/sda" then "btrfs device add
/dev/sdb" and same for sdc.
I am sure that i didn't explicitly use -m raid1 or raid10.
Is there a way that i can check this ?
If i do have raid0 for both metadata and data is there anything i can d=
o ?
I've been looking at the source but haven't got my head around it yet.
What whould happen if i just ignore/bypass the transid error?
The error:
[265889.197279] device fsid 734a485d12c77872-
9b0b5aa408670db4 devid 3 transid 39651 /dev/sda
[265889.198266] btrfs: use compression
[265889.647817] parent transid verify failed on 2721514774528 wanted
39651 found 39649
[265889.672632] btrfs: open_ctree failed
Or could i update the metadata to want 39649 ?
Thanks again!
On Thu, Dec 2, 2010 at 5:21 PM, Chris Mason <chris.mason@oracle.com> wr=
ote:
>
> 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 ver=
ify
> > 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? =A0Unless you formatted with -m raid0, the
> current git tree should be able to read this FS by using the second c=
opy
> of the metadata.
>
> -chris
--
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:[~2010-12-02 21:49 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
2010-12-02 21:49 ` Tommy Jonsson [this message]
[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='AANLkTimuUZM_j-MA0L6rSOOO2TTq=ap8j+=WjCRj6BL8@mail.gmail.com' \
--to=quazzie@gmail.com \
--cc=chris.mason@oracle.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 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).