From: "Grant Grundler" <grundler@google.com>
To: Marc Bejarano <beej@alum.mit.edu>
Cc: linux-raid@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: data corruption: ext3/lvm2/md/mptsas/vitesse/seagate
Date: Wed, 26 Mar 2008 10:03:08 -0700 [thread overview]
Message-ID: <da824cf30803261003i690f108dh86ff846e4f5fd2fa@mail.gmail.com> (raw)
In-Reply-To: <200803260217.m2Q2HsiU023202@colby.verdasys.com>
On Tue, Mar 25, 2008 at 7:17 PM, Marc Bejarano <beej@alum.mit.edu> wrote:
> At 20:12 3/25/2008, Grant Grundler wrote:
> >On Tue, Mar 25, 2008 at 4:43 PM, Marc Bejarano <beej@alum.mit.edu> wrote:
>
> >> having never played with blocktrace, i have no idea what it's
> >> capabilities are. can it be used to record not just the IOs, but
> >> also their timings? any other ideas? i'm at a loss for how to turn
> >> my reproducible test case into something i can send to seagate for
> >> investigation.
> >
> >Yes and yes (I think). But by itself, it won't help since block
> >trace tools don't generally do any data validation.
>
> we've been successfully using md's mirror consistency-checking
> capabilities to spot the corruption.
Oh? Have you been running disktest on the mirrors or the individual disks?
I was expecting the latter but wonder now.
> if we can get an IO pattern
> that reproduces the issue, we're golden. if only we didn't other
> things to do with our time that were actually productive for us
> ;) hopefully we'll be able to report back soon-ish with more.
*sigh* this can take a long time to track down. And you right that
getting the "magic" workload to reproduce is key.
>
> if anybody else has helpful ideas, we're all ears.
>
> thanks, grant!
welcome,
grant
>
> marc
>
>
next prev parent reply other threads:[~2008-03-26 17:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 21:08 data corruption: ext3/lvm2/md/mptsas/vitesse/seagate Marc Bejarano
2008-03-06 22:52 ` Steve Cousins
2008-03-07 22:39 ` Marc Bejarano
2008-03-08 17:18 ` Bill Davidsen
2008-03-08 21:23 ` Grant Grundler
2008-03-07 0:10 ` James Bottomley
2008-03-07 22:40 ` Marc Bejarano
2008-03-10 15:36 ` James Bottomley
2008-03-10 19:02 ` Janek Kozicki
2008-03-10 19:55 ` James Bottomley
2008-03-11 22:14 ` Marc Bejarano
[not found] ` <7.1.0.9.2.20080311174743.1376cc30@alum.mit.edu>
2008-03-25 23:43 ` Marc Bejarano
2008-03-26 0:12 ` Grant Grundler
[not found] ` <da824cf30803251712t801fdaexc19ba4fe8130ee2e@mail.gmail.com >
2008-03-26 2:17 ` Marc Bejarano
2008-03-26 17:03 ` Grant Grundler [this message]
[not found] ` <da824cf30803261003i690f108dh86ff846e4f5fd2fa@mail.gmail.co m>
2008-03-27 20:45 ` Marc Bejarano
[not found] ` <7.1.0.9.2.20080327163522.14ab0ac8@alum.mit.edu>
2008-09-02 19:32 ` Marc Bejarano
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=da824cf30803261003i690f108dh86ff846e4f5fd2fa@mail.gmail.com \
--to=grundler@google.com \
--cc=beej@alum.mit.edu \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@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