Their's no dmesg information at all before the hang. The system just
hangs suddenly without any kernel printk or oops.
mdadm version is debian lenny version 2.6.7.2-3
I will get mdadm -E & mdadm -D informations tomorrow but I doubt they
are useful.
Johnson
on 2010/11/24 22:19, Mathias BurÃn wrote:
Hi,
I suppose a few logs would be interesting. (dmesg, mdadm -E (hdds),
mdadm -D md10, zcat /proc/config.gz, mdadm version)
Regards,
// Mathias
2010/11/24 Du Jun<dujun@xxxxxxxxxxxxx>:
Hi,
We just quick tested the raid stability under the vanilla 2.6.36 kernel
and got an unstable result.
first, we create a raid5 array using 16 sata disks:
mdadm -C /dev/md10 -l 5 -n 16 /dev/sd[b-q]
then use dd to stress the io:
dd if=/dev/zero of=/dev/md10 bs=1M
After a while, usually several minutes, the system hangs. It looks like
some kind of kernel deadlock. ping to this machine could get timely
response, however, any other process just hangs.
It is easily reproducible and everytime the test result is a system hang.
Johnson
--
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
--
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
--
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
