From: Chris Mason <chris.mason@oracle.com>
To: Bill Pemberton <wfp5p@viridian.itc.virginia.edu>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: assertion failures
Date: Wed, 24 Feb 2010 19:40:04 -0500 [thread overview]
Message-ID: <20100225004004.GK25641@think> (raw)
In-Reply-To: <20100224134532.282174094A@viridian.itc.virginia.edu>
On Wed, Feb 24, 2010 at 08:45:32AM -0500, Bill Pemberton wrote:
> I've had 2 different filesystems fail in the same way recently. In
> both cases the server crashed (probably due to something unrelated to
> btrfs). On reboot the fsck fails as follows:
>
> # btrfsck /dev/raidvg/vol4
> parent transid verify failed on 20971520 wanted 206856 found 214247
I don't suppose you have the dmesg errors from the crash? This error
shows the header in the block is incorrect, so either something was
written to the wrong place or not written at all.
Have you memtest86 on this system?
How did it crash...was a power off used to reset the machine?
-chris
next prev parent reply other threads:[~2010-02-25 0:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 13:45 assertion failures Bill Pemberton
2010-02-25 0:40 ` Chris Mason [this message]
2010-02-25 14:04 ` Bill Pemberton
2010-02-25 18:28 ` Gustavo Alves
2010-02-26 16:13 ` Chris Mason
2010-02-26 16:15 ` Chris Mason
2010-02-26 19:57 ` Gustavo Alves
2010-02-26 21:10 ` Chris Mason
2010-02-26 21:26 ` Gustavo Alves
2010-02-26 16:17 ` Chris Mason
2010-02-26 16:41 ` Bill Pemberton
2010-02-26 17:59 ` Chris Mason
2010-02-26 18:11 ` Bill Pemberton
2010-02-26 19:09 ` Chris Mason
2010-02-26 20:43 ` Bill Pemberton
2010-02-26 20:49 ` Diego Calleja
2010-02-26 21:08 ` Chris Mason
2010-02-28 3:05 ` Cláudio Martins
2010-02-26 19:11 ` Mike Fedyk
2010-02-26 19:15 ` Chris Mason
2010-02-26 20:45 ` Bill Pemberton
2010-02-26 20:53 ` Chris Mason
2010-02-27 22:56 ` Bill Pemberton
2010-02-26 20:44 ` Bill Pemberton
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=20100225004004.GK25641@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wfp5p@viridian.itc.virginia.edu \
/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