I'm sorry, there's been an error in previous mail. I erroneously used old mdadm to create the array. > Additionally, I've tried this with mdadm 2.6.7, it goes as follows, > > [root@kylie raid-test]# ~kotek/mdadm-2.6.7/mdadm --zero-superblock > /dev/loop[012345] > [root@kylie raid-test]# /sbin/mdadm --create --verbose /dev/md55 > --chunk=256 -l 6 --raid-devices=4 /dev/loop0 /dev/loop1 /dev/loop2 > /dev/loop3 > mdadm: layout defaults to left-symmetric > mdadm: size set to 24832K > mdadm: array /dev/md55 started. > [root@kylie raid-test]# ~kotek/mdadm-2.6.7/mdadm --add /dev/md55 > /dev/loop4 /dev/loop5 > mdadm: added /dev/loop4 > mdadm: added /dev/loop5 > [root@kylie raid-test]# ~kotek/mdadm-2.6.7/mdadm --grow /dev/md55 > --raid-devices=6 > mdadm: Need to backup 1024K of critical section.. > mdadm: /dev/md55: failed to suspend device. > [root@kylie raid-test]# ~kotek/mdadm-2.6.7/mdadm --grow /dev/md55 > --raid-devices=6 > mdadm: Need to backup 1024K of critical section.. > mdadm: ... critical section passed. > [root@kylie raid-test]# If rerun, really with 2.6.7 --create, it does the "old" behaviour. That's how it looks: [root@kylie raid-test]# ~kotek/mdadm-2.6.7/mdadm --zero-superblock /dev/loop[012345] [root@kylie raid-test]# ~kotek/mdadm-2.6.7/mdadm --create --verbose /dev/md55 --chunk=256 -l 6 --raid-devices=4 /dev/loop0 /dev/loop1 /dev/loop2 /dev/loop3 mdadm: layout defaults to left-symmetric mdadm: size set to 24832K mdadm: array /dev/md55 started. [root@kylie raid-test]# ~kotek/mdadm-2.6.7/mdadm --add /dev/md55 /dev/loop4 /dev/loop5 mdadm: added /dev/loop4 mdadm: added /dev/loop5 [root@kylie raid-test]# ~kotek/mdadm-2.6.7/mdadm --grow /dev/md55 --raid-devices=6 mdadm: Need to backup 1024K of critical section.. mdadm: /dev/md55: failed to suspend device. [root@kylie raid-test]# ~kotek/mdadm-2.6.7/mdadm --grow /dev/md55 --raid-devices=6 mdadm: Need to backup 1024K of critical section.. ^C Sorry for the mess up, Cheers, Mike -- 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
