From: hpa@zytor.com (H. Peter Anvin)
To: linux-raid@vger.kernel.org
Subject: Re: [PATCH md 2 of 4] Fix raid6 problem
Date: Thu, 3 Feb 2005 02:12:38 +0000 (UTC) [thread overview]
Message-ID: <cts1am$6c8$1@terminus.zytor.com> (raw)
In-Reply-To: 33023.212.158.231.74.1106488921.squirrel@mail.fsck.co.uk
Followup to: <33023.212.158.231.74.1106488921.squirrel@mail.fsck.co.uk>
By author: "A. James Lewis" <james@fsck.co.uk>
In newsgroup: linux.dev.raid
>
>
> Sorry for the delay in replying, I've been using RAID6 in a real life
> situation with 2.6.9 + patch, for 2 months now, with 1.15Tb of storage,
> and I have had more than 1 drive failure... as well as some rather
> embarasing hardware corruption which I traced to a faulty IDE controller.
>
> Dispite some random DMA corrupion, and loosing a total of 3 disks, I have
> not had any problems with it RAID6 itself, and really it has litereally
> saved my data from being lost.
>
> I ran a diff against the 2.6.9 patch and what is in 2.6.10... and they are
> not the same, presumably a more elegant fix has been implimented for the
> production kernel??
>
I think there are some other (generic) fixes in there too.
Anyway... I'm thinking of sending in a patch to take out the
"experimental" status of RAID-6. I have been running a 1 TB
production server in 1-disk degraded mode for about a month now
without incident.
-hpa
next prev parent reply other threads:[~2005-02-03 2:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 23:56 [PATCH md 2 of 4] Fix raid6 problem A. James Lewis
2004-12-09 0:21 ` H. Peter Anvin
2004-12-09 0:35 ` Jim Paris
[not found] ` <200412090021.iB90L4MK014200@terminus.zytor.com>
2005-01-23 14:02 ` A. James Lewis
2005-01-23 14:42 ` Kevin P. Fleming
2005-02-03 2:12 ` H. Peter Anvin [this message]
2005-02-03 17:13 ` Andy Smith
[not found] <200502031145.j13Bj1fl016074@terminus.zytor.com>
2005-02-03 16:39 ` H. Peter Anvin
2005-02-03 16:59 ` Lars Marowsky-Bree
2005-02-03 17:06 ` H. Peter Anvin
2005-02-03 17:43 ` Guy
2005-02-03 18:07 ` H. Peter Anvin
2005-02-03 19:36 ` Gordon Henderson
2005-02-04 9:04 ` Andrew Walrond
2005-02-04 11:19 ` Gordon Henderson
2005-02-04 18:31 ` Mike Hardy
2005-02-13 21:05 ` Mark Hahn
2005-02-13 21:19 ` Gordon Henderson
2005-02-14 4:56 ` Tim Moore
2005-02-14 9:42 ` Andrew Walrond
2005-02-13 22:58 ` Mike Hardy
2005-02-13 23:14 ` Richard Scobie
2005-02-06 3:38 ` Tim Moore
2005-02-14 4:49 ` Tim Moore
2005-02-14 8:09 ` Gordon Henderson
2005-02-14 4:27 ` Tim Moore
2005-02-14 8:05 ` Gordon Henderson
-- strict thread matches above, loose matches on Subject: below --
2004-11-02 3:37 [PATCH md 0 of 4] Introduction NeilBrown
2004-11-02 3:37 ` [PATCH md 2 of 4] Fix raid6 problem NeilBrown
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='cts1am$6c8$1@terminus.zytor.com' \
--to=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).