Re: Data corruption after raid migration (raid5 to raid6 in 2.6.31 with mdadm 3.1)

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

 



Yeah, I did it the wrong way the first time and wound up with a raid-6
array that expected one more drive than I had.  It would be a lot
easier if I could have specified the target number of destination
stripes and then also specified the number of parity stripes.

I needed to reduce the added space back out, so that it could be added
as a parity device instead of another data-device.

On Thu, Nov 5, 2009 at 5:45 PM, KueiHuan Chen <kueihuan.chen@xxxxxxxxx> wrote:
> Dear Michael,
>
>   Did you also reduce the raid disks ? That operation need 2.6.32 and
> later. Others such like level change is working at 2.6.31.
>
> Thanks.
>
> Best Regards,
> KueiHuan-Chen
--
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