On Friday June 27, Markus@xxxxxxxxxxxxxxxxx wrote: > Hi, > > Am Freitag, 27. Juni 2008 08:51 schrieb NeilBrown: > > From: Chris Webb <chris@xxxxxxxxxxxx> > > Allow /sys/block/mdX/md/rdY/size to change on running arrays, moving the > > superblock if necessary for this metadata version. We prevent the available > > space from shrinking to less than the used size, and allow it to be set to > > zero to fill all the available space on the underlying device. > > I'm very happy of this new feature. But I'm a little confused how to use it > correctly. > Can md now recognize the change by itself and I only have to run mdadm --grow? > Or have I manually update /sys/block/mdX/md/rdY/size and afterwards run > mdadm --grow? No, md does not recognise the change by itself. Currently you need to update ..../size yourself before using "mdadm --grow" This should probably be incorporated into mdadm at some stage, but it hasn't yet. > > To be on the safe side I'd first lvresize one disk of the raid1, then do > mdadm --grow to let md update/move the superblock of this disk. And after > this is successful, lvresize the other disk and do mdadm --grow. So in case > of a failure i wouldn't loose the whole raid1!? > Am I correct or am I missing something? You don't want to "mdadm --grow" until everything has been resized. First lvresize one disk, then write '0' to the .../size file. Then do the same for the other disk. Then "mdadm --grow /dev/mdX --size max". 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
