On Sat, 24 Mar 2012 21:47:15 +0100 Markus Hochholdinger <Markus@xxxxxxxxxxxxxxxxx> wrote: > Hello, > > it's been a long time, but today I tried again and had success! > > Am 28.06.2008 um 01:41 Uhr schrieb Neil Brown <neilb@xxxxxxx>: > > On Friday June 27, Markus@xxxxxxxxxxxxxxxxx wrote: > > > Am Freitag, 27. Juni 2008 08:51 schrieb NeilBrown: > > > > From: Chris Webb <chris@xxxxxxxxxxxx> > [..] > > 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". > > it works for me, if I do: > echo 0 > /sys/block/md2/md/rd0/size > mdadm --grow /dev/md2 --size=max > # till here, nothing happens > echo 0 > /sys/block/md2/md/rd1/size > mdadm --grow /dev/md2 --size=max > # rebuild of the added space begins > > If I do only: > echo 0 > /sys/block/md2/md/rd0/size > echo 0 > /sys/block/md2/md/rd1/size > mdadm --grow /dev/md2 --size=max > nothing will change. That is odd.. it certainly should. And the current 'mdadm' will do the "echo 0 > size" for you so you just need to "mdadm --grow --size=max" command. > > As I understand, with "echo 0" md sees the new size and only with --grow the > superblock will be moved. No, the superblock is moved with the "echo 0", but the space isn't used until the "--grow". > > I'm doing this with 2.6.32-5-xen-686 within Debian (squeeze) 6.0. > > Many thanks to you and all the other linux-raid developers for this feature! > > I'm very happy about this :-) Excellent! Thanks, NeilBrown > >
Attachment:
signature.asc
Description: PGP signature
