linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: Neil Brown <neilb@suse.de>
Cc: John Rowe <rowe@excc.ex.ac.uk>, linux-raid@vger.kernel.org
Subject: Re: Expanding RAID array?
Date: Tue, 17 Jan 2006 10:43:44 +0400	[thread overview]
Message-ID: <43CC9220.8000800@wasp.net.au> (raw)
In-Reply-To: <17356.8228.325002.652805@cse.unsw.edu.au>

Neil Brown wrote:

> - add disks to convert to raid6.
>     I don't think this is possible, but you should check the latest
>     raid reconfig.

It's not. I started work on it Feb last year but then real life got in the way again.
In the longer term, I think raidreconf as it stands is going to die (mainly because it's 
infrastructure relies on the old raidtab architecture). I thought about perhaps porting it as an 
addon to mdadm, but then I ran out of drives/machines/time to test it on.

>     Might be supported online with a limited raid6 in which the Q
>     syndrome (second 'parity' block) isn't rotated among disks.

In theory I would have thought it not that much different than a raid-5 expand, just inserting an 
extra block for the Q syndrome.

> - status of RAID6
>     I believe it is as stable/reliable as raid5.

Mine has been running since Feb last year with fairly moderate use and no hiccups.
I have just upgraded to the latest 2.6.15-git on that machine to give some of the newer raid patches 
(like check & repair) a whirl. Seems fairly solid.

Let's say I've never had any raid-6 related data loss, or even near misses, but it has saved my 
bacon in 2 dual drive failures in the last year.

Oh, and the new read and check code (rather than just rebuild the parity blocks) shaves about 1 hour 
of what was an 11 hour rebuild time on this particular raid-6. Thanks Neil!

Regards,
Brad
-- 
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams

      parent reply	other threads:[~2006-01-17  6:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-16 15:14 Expanding RAID array? John Rowe
2006-01-16 22:37 ` Neil Brown
2006-01-16 22:48   ` Gordon Henderson
2006-01-16 23:37     ` Jacob Schmidt Madsen
2006-01-17  7:30       ` Eyal Lebedinsky
2006-01-23 14:28     ` Turbo Fredriksson
2006-01-16 23:30   ` JaniD++
2006-01-17  0:52     ` Neil Brown
2006-01-17  6:43   ` Brad Campbell [this message]

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=43CC9220.8000800@wasp.net.au \
    --to=brad@wasp.net.au \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=rowe@excc.ex.ac.uk \
    /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).