On Friday September 2, [EMAIL PROTECTED] wrote: > In doing some benchmarking, I've found a curious problem - after > creating an array the resync has stalled at 99.7%: > > [EMAIL PROTECTED] ~]# cat /proc/mdstat > Personalities : [raid6] > md0 : active raid6 sdm1[11] sdl1[10] sdk1[9] sdj1[8] sdi1[7] sdh1[6] > sdg1[5] sdf1[4] sde1[3] sdd1[2] sdc1[1] sdb1[0] > 4963200 blocks level 6, 32k chunk, algorithm 2 [12/12] > [UUUUUUUUUUUU] > [===================>.] resync = 99.7% (496320/496349) > finish=0.0min speed=628K/sec > unused devices: <none>
$ bc -l bc 1.06 Copyright 1991-1994, 1997, 1998, 2000 Free Software Foundation, Inc. This is free software with ABSOLUTELY NO WARRANTY. For details type `warranty'. 496349/32 15510.90625000000000000000 15510*32 496320 Get the picture? I suspect you are using mdadm-2.0 - yes? This is a bug triggered by they way mdadm 2.0 creates arrays (differently to 1.x). It is fixed in 2.6.13. > The command used to create the aray was: > > mdadm -C /dev/md0 -l6 -n12 -c 32 -z 496349 /dev/sd[b-m]1 > If you replace 496349 with 496320, it should work fine. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
