linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Paris <jim@jtan.com>
To: Brad Campbell <brad@wasp.net.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID-6: help wanted
Date: Sun, 24 Oct 2004 02:46:51 -0400	[thread overview]
Message-ID: <20041024064651.GA5343@jim.sh> (raw)
In-Reply-To: <417B3CF9.7090107@wasp.net.au>

> >There is currently a data-corruption bug in the RAID-6 md layer
> >(raid6main.c).  I have so far not been successful in locating it,
> >although it is easily reproducible, thanks to a set of scripts by Jim
> >Paris.  I suspect it is a race condition between raid6d and the rest
> >of the kernel.
> 
> Great, can we get a copy of the scripts to try and assist?

Sure:

---

Date: Fri, 6 Aug 2004 00:04:39 -0400
From: Jim Paris <jim@jtan.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Kernel panic, FS corruption  Was: Re: Call for RAID-6 users

> If you can reproduce it with ext2/3 it would make debugging simpler, 
> because I understand the ext code and data structures a lot better.

This demonstrates it on ext2.  I can't seem to reproduce it with just
simple use of 'dd', but it shows up if I untar a ton of data.

This script:
- creates five 100MB "disks" through loopback
- puts them in a six-disk RAID-6 array (resulting size=400MB, degraded)
- untars about 350MB of data to the array
- runs e2fsck, which shows filesystem errors

Usage: 
- put r6ext.sh and big.tar.bz2 in a directory
- run r6ext.sh as root

Sorry for the huge files, but e2fsck didn't show any problems when I
scaled everything down by a factor of 10.  You could probably make
your own big.tar.bz2 and see the same problem, as there's nothing
special about this data.

  http://stonewall.mit.edu/~jim/r6ext.sh
  http://stonewall.mit.edu/~jim/big.tar.bz2 (77MB)

-jim

  reply	other threads:[~2004-10-24  6:46 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-23 23:46 RAID-6: help wanted H. Peter Anvin
2004-10-24  5:26 ` Brad Campbell
2004-10-24  6:46   ` Jim Paris [this message]
     [not found]   ` <417B546C.3050706@zytor.com>
2004-10-24  7:09     ` H. Peter Anvin
2004-10-24  7:17       ` H. Peter Anvin
2004-10-24  7:18       ` Brad Campbell
2004-10-25  5:41 ` Neil Brown
2004-10-25  6:20   ` Jim Paris
2004-10-25  6:24     ` Neil Brown
2004-10-25  6:33       ` Jim Paris
2004-10-25 14:23       ` H. Peter Anvin
2004-10-27  3:38     ` Neil Brown
2004-10-27  5:23       ` H. Peter Anvin
2004-10-27  6:00         ` Jim Paris
2004-10-27  6:03           ` H. Peter Anvin
2004-10-28  1:17           ` H. Peter Anvin
2004-10-28 16:00             ` Jim Paris
2004-10-28 17:48               ` H. Peter Anvin
2004-10-28 17:49               ` H. Peter Anvin
2004-10-29  0:43                 ` Neil Brown
2004-10-29 11:48                   ` Jim Paris
2004-10-29 12:56                     ` Guy
2004-10-29 18:15                       ` Jim Paris
2004-10-29 19:04                         ` H. Peter Anvin
2004-10-29 19:21                           ` Jim Paris
2004-10-29 19:33                             ` H. Peter Anvin
2004-10-29 20:28                             ` Guy
2004-10-29 20:32                               ` H. Peter Anvin
2004-10-29 21:21                                 ` Guy
2004-10-29 21:33                                   ` H. Peter Anvin
2004-10-29 12:29                   ` Guy
2004-10-27  5:56       ` H. Peter Anvin

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=20041024064651.GA5343@jim.sh \
    --to=jim@jtan.com \
    --cc=brad@wasp.net.au \
    --cc=linux-raid@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).