On 12/06/2015 04:13 PM, David Waite wrote: > >> On Dec 6, 2015, at 1:35 PM, Phil Turmel <philip@xxxxxxxxxx> wrote: >> >> On 12/05/2015 10:04 PM, David Waite wrote: >>> I’m having difficulty shrinking down a RAID6 array (md2) on a Sinology NAS. I wish to go from 13 drives to 11, and believe I need to go to 12 first to maintain operation and redundancy through the resizing process. >> >> No, you can go straight to 11 if you've set array-size properly. --grow >> operations maintain redundancy throughout. > > I thought —grow maintains redundancy for power loss but not disk failure. > > Would I do this by simply marking the other drive I want to remove as failed? No! Is that what you did with the other one? --grow with a reduction in number leaves the unneeded drive(s) as hot spares when it is complete. That's when you remove them. Or, if it didn't pick the drives you wanted to remove, you can then do a --replace operation, which also maintains redundancy throughout. > I’ll try —array-size again. How is the array-size suggestion by mdadm calculated - the drives are not of uniform size. You didn't post your --detail and --examine output as requested, so I can't be specific. For parity arrays, the size of the smallest member controls the size of the array. Phil -- 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
