Chris Webb <chris@xxxxxxxxxxxx> writes: > I just tried growing the slots up from 1G to 3G, then > > echo $((2097136 + 2*1024*1024*2)) >/sys/block/md127/md/resync_start > mdadm --grow 3145720 > > but this gives me > > md127 : active raid1 dm-3[1] dm-2[0] > 3145720 blocks super 1.1 [2/2] [UU] > resync=PENDING > > in /proc/mdstat, which is presumably not right? Rewriting the original value of 18446744073709551615 back to /sys/block/md127/md/resync_start removes this, although it looks like any value lower than this gives a PENDING state. Presumably this means that:- echo 18446744073709551614 >/sys/block/md127/md/resync_start mdadm --grow --size=... /dev/md127 echo 18446744073709551615 >/sys/block/md127/md/resync_start is a generic recipe for growing an array 'assume-clean' without needing to know anything more about the eventual size of the array other than the parameter passed to --size= (max or component size). -- 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
