linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Kuther <gimpel@sonnenkinder.org>
To: The development of BTRFS <linux-btrfs@vger.kernel.org>
Cc: Chris Mason <chris.mason@oracle.com>
Subject: Re: volume broken? btrfsck fails
Date: Wed, 4 Aug 2010 20:48:40 +0200	[thread overview]
Message-ID: <20100804204840.1652f4cd@gimpel.ath.cx> (raw)
In-Reply-To: <20100707001622.GH15984@think>

On Di, 06.07.10 20:16 Chris Mason <chris.mason@oracle.com> wrote:

> On Sat, Jun 26, 2010 at 03:15:04PM -0700, Yee-Ting Li wrote:
> > Hi,
> > 
> > i think my btrfs volume is hosed.... it mounts okay, but iostat
> > shows /dev/sdg on 100% load. dmesg shows lots of 'parent transid
> > verify failed on x wanted y found z'. then after a while i can't
> > read from it (access to the filesystem freezes).
> > 
> > the machine had crashed (prob from some other process), and upon
> > reboot i've been experience this problem since.
> > 
> > can anyone provide any guidance in how to proceed?
> 
> These are definitely corruptions, and they probably came from the
> crash. Can you tell me more about the crash? (Power failure, what is
> the storage underneath etc, what are the write cache settings).  We
> don't expect these kinds corruptions to happen.
> 
> Yan Zheng is making a lot of progress on btrfsck, but I don't think
> you'll want to be one of the first testers there.  I can definitely
> help copy things off if you're having trouble accessing the FS.
> 
> -chris

Hello Chris,

sorry if I'm hijacking this thread. I got a similar problem, probably
caused by a system crash due to faulty/badly timed memory dimms. The
system suddenly hardlocked during write activity.

- kernel is 2.6.35
- btrfs on top of a md raid5, which looks healthy. Desktop SATA disks.

# cat /proc/mdstat|grep -A1 md0
md0 : active raid5 sdb1[0] sdd1[1] sdc1[2]
      2930271872 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]

# btrfsck
usage: btrfsck dev
Btrfs v0.19-16-g075587c-dirty

# btrfsck /dev/md0
parent transid verify failed on 2419218964480 wanted 127839 found 127260
parent transid verify failed on 2419218964480 wanted 127839 found 127260
parent transid verify failed on 2419218915328 wanted 127839 found 127260
parent transid verify failed on 2419218915328 wanted 127839 found 127260
parent transid verify failed on 2419214266368 wanted 127839 found 127837
parent transid verify failed on 2419214266368 wanted 127839 found 127837
parent transid verify failed on 2419214266368 wanted 127839 found 127837
Segmentation fault

Mount endlessly loops, like explained in this thread.

If there is a way, I would really like some aid copying the data off.
The backup is quite out of date, shame on me.

Best regards,
Thomas

  parent reply	other threads:[~2010-08-04 18:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-26 22:15 volume broken? btrfsck fails Yee-Ting Li
2010-07-01 12:51 ` Daniel Kozlowski
2010-07-04  6:57   ` Yee-Ting Li
2010-07-07  0:19   ` Chris Mason
2010-07-08  0:21     ` Daniel Kozlowski
2010-07-08  2:39       ` Daniel Kozlowski
2010-07-12  0:50         ` Chris Mason
2010-07-08  8:43       ` Daniel J Blueman
2010-07-07  0:16 ` Chris Mason
2010-07-07  5:23   ` Yee-Ting Li
2010-08-04 18:48   ` Thomas Kuther [this message]
2010-08-05  1:30     ` Chris Mason
2010-08-14 11:08       ` Thomas Kuther
2010-07-11  8:19 ` Yee-Ting Li
2010-07-12  0:43   ` Chris Mason
2010-07-12  4:05     ` Yee-Ting Li

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=20100804204840.1652f4cd@gimpel.ath.cx \
    --to=gimpel@sonnenkinder.org \
    --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).