Hi Neil, As requested, here is more background. On 02/10/11 11:28, Iordan Iordanov wrote:
We are currently using 2.6.36 on a production machine running mdadm
Our distribution is Debian Lenny. We have 10 3-way RAID1 mirrors (30 1TB disks) striped together with LVM in one large volume group, out of which we create logical drives. The actual drives are iscsi targets we import from separate machines. The system is serving about 3500 active (not logged-in at the same time) accounts to our department. Also, we have a "development" platform, with no users using it, also with lvm, mdadm, and iscsi, but with 5 disks instead of 30. The development platform was sitting idle the whole time.
this morning we experienced a very similar issue, but we didn't have the LOCKUP_DETECTOR config options set, so there was absolutely no output.
What I mean by a similar issue is that our development platform hung without any output in the logs and was completely unresponsive on Feb 7, and our production system hung and was completely unresponsive, save for pings, on Feb 10. I don't know if the two hangs were caused by the same issue.
I thought that the potential lock-up reported by Du Jun was acknowledged as reality. I was wrong. We will recompile a longterm kernel (this time) with the LOCKUP_DETECTOR flags set, and will wait to see if the issue recurs. Do you have any suggestions to us?
Many thanks, Iordan -- 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
