From: Tim Small <tim@buttersideup.com>
To: "Buehl, Reiner" <reiner.buehl@hp.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: ext3 filesystem corruption on md RAID1 device
Date: Thu, 20 May 2010 12:49:30 +0100 [thread overview]
Message-ID: <4BF521CA.7080503@buttersideup.com> (raw)
In-Reply-To: <BA8A2107B0FD8A48AEB0405BDC36CE4F3F48B1DCFD@GVW1115EXC.americas.hpqcorp.net>
Buehl, Reiner wrote:
> The two disks used in the RAID1 md device are both Seagate ST31000528AS that show no errors in long and short SMART test and Seatools. Memtest shows no memory problems.
Have you tried:
echo 'check' > /sys/block/md<whatever>/md/sync_action
... that should report discrepancies between the two sides of the mirror
... Unfortunately, I don't think it reports which LBAs, but you could
find this by hand using dd and md5sum or whatever. After that, if you
do have discrepancies, then you can investigate what form they take by
comparing the blocks from the individual block devices, and viewing them
in a hex editor etc. etc.
Tim.
next prev parent reply other threads:[~2010-05-20 11:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 10:08 ext3 filesystem corruption on md RAID1 device Buehl, Reiner
2010-05-20 10:56 ` Dmitry Monakhov
2010-05-20 11:10 ` Buehl, Reiner
2010-05-20 11:27 ` Dmitry Monakhov
2010-05-20 11:35 ` Buehl, Reiner
2010-05-20 11:49 ` Tim Small [this message]
2010-05-20 12:04 ` Buehl, Reiner
2010-05-20 14:30 ` tytso
2010-05-21 14:40 ` Buehl, Reiner
2010-05-23 3:21 ` Buehl, Reiner
2010-05-23 5:46 ` Buehl, Reiner
2010-05-27 20:12 ` Jan Kara
2010-05-29 13:48 ` Buehl, Reiner
2010-05-31 20:55 ` Jan Kara
2010-06-01 7:25 ` Buehl, Reiner
[not found] ` <20100601102240.GA4275@quack.suse.cz>
2010-06-18 7:12 ` Buehl, Reiner
2010-06-18 11:09 ` Bug#582275: " Theodore Tso
2010-06-18 11:25 ` Theodore Tso
2010-05-21 4:40 ` Robert Hancock
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=4BF521CA.7080503@buttersideup.com \
--to=tim@buttersideup.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=reiner.buehl@hp.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).