linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 16:50:42 -0500	[thread overview]
Message-ID: <1291326502-sup-1726@think> (raw)
In-Reply-To: <AANLkTim5-5KQ3_sEb9WY+O1Uj36=3M3i_yQKeuSb7Qe5@mail.gmail.com>

Excerpts from Tommy Jonsson's message of 2010-12-02 16:45:39 -0500:
> 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 ?

The defaults will maintain raid1 as you add more drives.  We can check
it with btrfs-debug-tree from the git repository.  But, more below.

> 
> If i do have raid0 for both metadata and data is there anything i can do ?
> 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 ?

The first thing I would try is:

git pull git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs-unstable.git

Build the latest tools, then:

btrfsck -s 1 /dev/xxx
btrfsck -s 2 /dev/xxx

If either of these work we have an easy way to get it mounted.  Just let
me know.

-chris

  parent reply	other threads:[~2010-12-02 21:50 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
     [not found]   ` <AANLkTim5-5KQ3_sEb9WY+O1Uj36=3M3i_yQKeuSb7Qe5@mail.gmail.com>
2010-12-02 21:50     ` Chris Mason [this message]
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=1291326502-sup-1726@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).