Your config is sufficient. Hard to say why it did not reboot. Ping the debian mailing list to see if there are reports of the same on whatever kernel you are on.
As far as the reason for it goes, there should have been a message just prior to the Kernel Panic message. Most likely reason is that it hit a on disk corruption. I would suggest fscking the device. On 05/09/2011 05:51 AM, Xavier Diumé wrote:
We have two servers with Debian 6.0. Both have multipath and iscsi lun's from Equallogic. All volumes are in a cluster named kvmcluster. It was working well but after an iscsiadm login on first server we got: Kernel Panic - not syncing : ocfs2 (device dm-18 panic forced after error) Server will reboot after 30 seconds... But the server didn't reboot. We have to shutdown manually. The system is virtualizing some systems and obviously all of them got down. /proc/sys/kernel/panic 30 /proc/sys/kernel/panic_on_oops 1 Why the system didn't reboot? We have to configure something else? Which problem may cause an ocfs2 error? Thanks, -- Xavier Diumé _______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
_______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
