From: Brad Campbell <brad@wasp.net.au>
To: linux-raid@vger.kernel.org
Subject: Raidreconf and raid-6
Date: Tue, 23 Mar 2004 17:25:59 +0400 [thread overview]
Message-ID: <40603AE7.4050301@wasp.net.au> (raw)
G'day all,
I'm in the middle of adding journaling to raidreconf to try and make it resilient to any failures
except hard disk failures (Power fails, reboots and that kind of thing). It's not pretty, and it
slows the process down something chronic but hopefully it will make the process bulletproof.
While I'm here I'm looking at trying to add raid-6 support also. I have had a pretty good trawl
through the raid-6 kernel code and given raidreconf does not do anything with parity blocks it looks
pretty similar to raid-5 from that respect.
Are there any gotchas that anyone can think of I should look out for that may trip me up with the
difference between raid5 & 6 ?
I figure if you could do an easy conversion between raid-5 and raid-6 it might speed up testing and
adoption of raid-6.
Regards,
Brad
next reply other threads:[~2004-03-23 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 13:25 Brad Campbell [this message]
2004-03-30 22:24 ` Raidreconf and raid-6 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=40603AE7.4050301@wasp.net.au \
--to=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).