Hi, Everything works fine right now, all I have to do after reboot was assemble array using backup file and set MDADM_GROW_ALLOW_OLD=1 enviroment variable. Thanks for your help. 2014/1/3 Phil Turmel <philip@xxxxxxxxxx>: > On 01/03/2014 08:34 AM, Piotr Klimek wrote: >> 2014/1/3 Phil Turmel <philip@xxxxxxxxxx> >> >>> >>>> After couple of days reshape stalled on 2147483648 block. I have found >>> that >>>> this is a bug in mdadm. 2147483648 is max integer on 32 bit system. For >>> now >>>> situation looks like this: >>> >>> You'll certainly have to take production down long enough to let a newer >>> kernel finish the reshape. Or you could be brave and replace the kernel >>> and let production continue through the balance of the reshape. >>> >> >> Is it safe to reboot during reshape and boot up with new kernel? I can >> easly upgrade kernel to 3.2.0. >> > > It is supposed to be safe. With a clean shutdown, the superblock will > have a record of the reshape progress and will be able to continue after > re-assembly. > > But you'll probably have to assembly manually to specify the location of > the critical section backup file. If your root FS is in this array, > you'll have to intervene in the initramfs. > > HTH, > > Phil -- Pozdrawiam Piotr Klimek -- 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
