Hi,
I think I've hit a reproducible bug in the raid 10 driver, tried on two
different machines with kernels 2.6.20 and 2.6.18. This is a script to
simulate the problem:
======================
#!/bin/bash
modprobe loop
for ID in 1 2 3 ; do
echo -n "Creating loopback device $ID... "
dd if=/dev/zero of=dsk${ID}.img bs=512 count=995967
losetup /dev/loop${ID} dsk${ID}.img
echo "done."
done
mdadm -C /dev/md2 -l 10 -n 3 -p o2 -c 2048 /dev/loop1 /dev/loop2 /dev/loop3
echo "Raid device assembled, check /proc/mdstat's output when resync is
finished"
======================
This is the output I get in /proc/mdstat after the resync settles:
======================
md2 : active raid10 loop3[2] loop2[3](F) loop1[0]
746496 blocks 2048K chunks 2 offset-copies [3/2] [U_U]
======================
-
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
