Re: raid5 resize in 2.6.17 - how will it be different from raidreconf?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Monday May 22, Dexter.Filmore@xxxxxx wrote:
> How will the raid5 resize in 2.6.17 be different from raidreconf? 

It is done (mostly) in the kernel while the array is active, rather
than completely in user-space while the array is off-line.

> Will it be less risky to grow an array that way?

It should be.  In particular it will survive an unexpected reboot (as
long as you don't lose and drives at the same time) which I don't
think raidreconf would.
Testing results so far are quite positive.


> Will it be possible to migrate raid5 to raid6?
> 

Eventually, but no time frame yet.

> (And while talking of that: can I add for example two disks and grow *and* 
> migrate to raid6 in one sweep or will I have to go raid6 and then add more 
> disks?)

Adding two disks would be the preferred way to do it.
Add only one disk and going to raid6 is problematic because the
reshape process will be over-writing live data the whole time, making
crash protection quite expensive.
By contrast, when you are expanding the size of the array, after the
first few stripes you are writing to an area of the drives where there
is no live data.

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux