From: Brad Campbell <brad@wasp.net.au>
To: RAID Linux <linux-raid@vger.kernel.org>
Subject: raid6 raidreconf progress
Date: Thu, 22 Apr 2004 18:52:49 +0400 [thread overview]
Message-ID: <4087DC41.8060206@wasp.net.au> (raw)
In-Reply-To: <4087C14D.6030605@wasp.net.au>
Brad Campbell wrote:
> G'day all,
>
> I'm currently adding raid6 support to raidreconf, and as part of my
> testing I'm doing all sorts of
> nasty things to a 200GB usb2 hard disk.
Ok, false alarm (sort of, I'm still interested in what happens with odd device sizes), but it was a
thinko in the raid6 parity block locator.
We have liftoff. It has now performed 2 raid5->raid6 and back again cycles.
I test it by using dd to dump 400mb of /dev/urandom to the device and then running md5sum on it, so
far we have 4 complete cycles to differing devices in different orders and different sizes (As long
as it stays above 400MB of course) and it's all good.
Hope to have something cleaned up and presentable in the near future.
Brad
next prev parent reply other threads:[~2004-04-22 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 12:57 raid6 creation with mdadm Brad Campbell
2004-04-22 14:52 ` Brad Campbell [this message]
2004-05-04 20:18 ` raid6 raidreconf progress 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=4087DC41.8060206@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).