On 01/02/2017 10:24 AM, Roman Mamedov wrote: > On Mon, 2 Jan 2017 09:55:34 -0600 > Benjammin2068 <benjammin2068@xxxxxxxxx> wrote: > >> >> On 01/02/2017 06:19 AM, Wols Lists wrote: >>> On 02/01/17 10:18, Benjammin2068 wrote: >>>> I get stuck at the --size max. >>>> >>>> it seems the correct syntax is "--size=" but that "max" is not supported as an argument. > First you say it's unsupported as an argument, but then actually > >>> [root@quantum ~]# mdadm --grow /dev/md1 --size max >>> mdadm: component size of /dev/md1 unchanged at 239490048K >>> [root@quantum ~]# mdadm --grow /dev/md1 --size=max >>> mdadm: component size of /dev/md1 unchanged at 239490048K > Unsupported as an argument looks like that: > >> mdadm --grow /dev/md1 --size=blah >> mdadm: invalid size: blah Sorry bout that -- when I said "unsupported" - it was from the combined results that there is no mention of it in the man page even though the Wiki mentions it and the results are ambiguous in actual use. > In your case mdadm appears to think there is nowhere to grow the array. > > Check with "blockdev --getsz /dev/sda3" and sdb3 that they actually do have a > proper size (the result will be in 512-byte sectors). > > If not, maybe your kernel didn't re-read the partition table after resizing > partitions (if that was what you did)? > > If the blockdevice size is wrong, do a "blockdev --rereadpt /dev/sda" and sdb, > or just rebooting (as in some cases rereading will fail with a "device busy" > error). > Yep -- sizes are off and --rereadpt returns "device busy". Be right back.... -Ben -- 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
