From: Jim Paris <jim@jtan.com>
To: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: RAID-6 corruption
Date: Thu, 29 Jul 2004 17:20:46 -0400 [thread overview]
Message-ID: <20040729212046.GA27332@jim.sh> (raw)
[-- Attachment #1: Type: text/plain, Size: 689 bytes --]
Hello,
(I've posted some messages about this to linux-raid, but haven't
gotten much of a response; this time I'm cc'ing to linux-kernel)
I am seeing reproducible corruption with software RAID-6 on an array
that has been created with missing disks. The attached script
demonstrates this easily through loopback devices, but I see the
problem just the same on real drives.
I do not see the problem with full RAID-6 arrays (no missing disks),
nor do I see it on RAID-5 arrays on the same system. I haven't seen
the corruption when writing directly to the md device, but I haven't
tested that very much.
Tested on 2.6.6, 2.6.7, 2.6.8-rc2, with mdadm 1.5.0 and 1.6.0.
See attached.
-jim
[-- Attachment #2: r6test.sh --]
[-- Type: application/x-sh, Size: 965 bytes --]
next reply other threads:[~2004-07-29 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 21:20 Jim Paris [this message]
2004-07-30 15:47 ` RAID-6 corruption 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=20040729212046.GA27332@jim.sh \
--to=jim@jtan.com \
--cc=linux-kernel@vger.kernel.org \
--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).