linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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
Date: Thu, 5 Aug 2004 20:19:09 -0400	[thread overview]
Message-ID: <20040806001909.GA19760@jim.sh> (raw)
In-Reply-To: <ceuhbm$rgs$1@terminus.zytor.com>

> > > I eventually got a kernel panic when copying large amounts of data to a 
> > > [degraded] raid6 array, which this time was the full 600 GB size.
> > > Don't know if it is helpful to anyone but info below:
> > 
> > The panic is from reiserfs, and it's occuring because the FS is
> > getting corrupted due to the raid6 problems.
> 
> It's still very odd to me that so far the only thing that triggers
> this kind of problems is reiserfs.  Either reiserfs just has a really
> odd series of access patterns, or it is relying on behaviour which
> isn't actually guaranteed.  I suspect the former, but it's still odd.

No, I did see the same corruption with XFS; it just took more work
before it would show up (ie. I couldn't get it to show up by simply
copying one huge file; I had to untar a full filesystem onto it).
So I would suspect the odd access patterns.  I could also run a test
with EXT2/3 if you'd like.  I didn't manage to trigger the corruption
directly on the md device, but my access pattern was quite simple in
that case (dd big blocks to different areas).

Are you able to reproduce the problem with the scripts I sent earlier?
If not, I can give you access to a machine that can.

-jim

  reply	other threads:[~2004-08-06  0:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 23:32 Call for RAID-6 users H. Peter Anvin
2004-07-26 21:38 ` Jim Paris
2004-07-27  2:05   ` Matthew - RAID
2004-07-27  2:12     ` Jim Paris
2004-07-27 16:40       ` Ricky Beam
2004-07-27 17:20         ` Jim Paris
2004-07-27 18:19           ` Jim Paris
2004-07-27 18:48             ` Jim Paris
2004-07-28  3:09               ` Jim Paris
2004-07-28  8:36                 ` David Greaves
2004-07-28 10:02                   ` Jim Paris
2004-07-30 15:58   ` H. Peter Anvin
2004-07-30 19:39     ` Jim Paris
2004-07-30 19:45       ` H. Peter Anvin
2004-07-30 21:11 ` maarten van den Berg
2004-07-30 21:38   ` maarten van den Berg
2004-07-31  0:28     ` maarten van den Berg
2004-08-01 13:03       ` Kernel panic, FS corruption Was: " maarten van den Berg
2004-08-01 18:05         ` Jim Paris
2004-08-01 22:10           ` maarten van den Berg
2004-08-05 23:54           ` H. Peter Anvin
2004-08-06  0:19             ` Jim Paris [this message]
2004-08-06  0:36               ` H. Peter Anvin
2004-08-06  4:04                 ` Jim Paris
2004-08-05 23:51     ` H. Peter Anvin
2004-08-05 23:46   ` 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=20040806001909.GA19760@jim.sh \
    --to=jim@jtan.com \
    --cc=hpa@zytor.com \
    --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).