From: Chris Mason <chris.mason@oracle.com>
To: Yee-Ting Li <yee379@gmail.com>
Cc: The development of BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: volume broken? btrfsck fails
Date: Tue, 6 Jul 2010 20:16:22 -0400 [thread overview]
Message-ID: <20100707001622.GH15984@think> (raw)
In-Reply-To: <569BCC7F-1920-4AC4-8069-369419029373@gmail.com>
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
next prev parent reply other threads:[~2010-07-07 0:16 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 [this message]
2010-07-07 5:23 ` Yee-Ting Li
2010-08-04 18:48 ` Thomas Kuther
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=20100707001622.GH15984@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=yee379@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).