https://bugzilla.novell.com/show_bug.cgi?id=241981 Summary: kernel 2.6.16.27-0.6-smp breaks OCFS2 Product: SUSE Linux 10.1 Version: Final Platform: x86-64 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: ken@turnkey.com.au QAContact: qa@suse.de When I applied the security update from kernel 2.6.16.21-0.25-smp to 2.6.16.27-0.6-smp, OCFS2 stopped working for my cluster. It works if there is only one member in the cluster. This is what happens on the first cluster member, ls2, when a second node, ls1, tries to join. The ls2 kernel panics and reboots. Feb 3 22:22:45 ls2 kernel: ocfs2_dlm: Nodes in domain ("CA52753AD4C1442BAABF6EEEB28AE450"): 0 1 Feb 3 22:22:45 ls2 kernel: kjournald starting. Commit interval 5 seconds Feb 3 22:22:45 ls2 kernel: ocfs2: Mounting device (8,17) on (node 1, slot 1) Feb 3 22:22:51 ls2 kernel: o2net: connection to node ls1 (num 0) at 192.168.200.82:7777 has been idle for 10 seconds, shutting it down. Feb 3 22:22:51 ls2 kernel: (0,1):o2net_idle_timer:1314 here are some times that might help debug the situation: (tmr 1170501761.628948 now 1170501771.628571 dr 1170501766.630927 adv 1170501766.630937:1170501766.630937 func (3dd3b117:505) 1170501765.647625:1170501765.647630) Feb 3 22:22:51 ls2 kernel: o2net: no longer connected to node ls1 (num 0) at 192.168.200.82:7777 ls2 rebooted here. On ls1, the log has these entries: Feb 3 22:22:41 ls1 kernel: o2net: accepted connection from node ls2 (num 1) at 192.168.200.83:7777 Feb 3 22:22:45 ls1 kernel: ocfs2_dlm: Node 1 joins domain CA52753AD4C1442BAABF6EEEB28AE450 Feb 3 22:22:45 ls1 kernel: ocfs2_dlm: Nodes in domain ("CA52753AD4C1442BAABF6EEEB28AE450"): 0 1 Feb 3 22:22:51 ls1 kernel: o2net: no longer connected to node ls2 (num 1) at 192.168.200.83:7777 ls1 does not reboot. Reverting to kernel 2.6.16.27-0.6-smp on all cluster members restored normal functioning. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.