DLM BACKUP EXEC CODE

There is only one process on each node which access the shared files as I explained. > there was no process which was holding a lock and thus blocking the process in > application requirements, there may be better solutions.

DLM BACKUP EXEC CODE

That appears to be the code path in question. > I assume from the report that the application is making use of fcntl POSIX Used NICs: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz > Can you tell me which NICs the cluster is using, and which firmware version the Additional comment from on 10:37:31 EST. To debug a posix lock problem, the following information from both nodes would be a good start: Additional comment from on 10:24:19 EST. Can you confirm that there was no process which was holding a lock and thus blocking the process in question? Depending on the application requirements, there may be better solutions. I assume from the report that the application is making use of fcntl POSIX locks. Additional comment from on 09:53:27 EST -Д¬an you tell me which NICs the cluster is using, and which firmware version the NICs are using, if applicable. Set to ? to ensure that it is properly evaluated for this release. Since this issue was entered in bugzilla, the release flag has been Additional comment from on 09:43:34 EST. Version-Release number of selected component (if applicable): 'echo 0 > /proc/sys/kernel/hung_task_timeout_secs' disables this message. INFO: task java:29180 blocked for more than 120 seconds. Java 29389 therfert 118uw REG 253,4 19 2394846 /mnt/jbm/common/therfert/nodeA/hornetq/journal/server.lock

Java 29389 therfert 90uw REG 253,4 19 2394838 /mnt/jbm/common/therfert/nodeB/hornetq/journal/server.lock Java 29389 therfert 57u REG 253,4 1048576 2395114 /mnt/jbm/common/therfert/nodeA/hornetq/bindings/hornetq-bindings-2.bindings Java 29389 therfert 45u REG 253,4 1048576 2394856 /mnt/jbm/common/therfert/nodeA/hornetq/bindings/hornetq-bindings-1.bindings The following files are opened when the process becomes zombie:

You can find this file from both nodes attached. I saved /sys/kernel/debug/gfs2/jbm:jbm/glocks before kill and after kill and there are no differences. When one node is rebooted, the zombie process on the other node finishes automatically.

So the result is unkillable zombie process on both nodes. When the process is killed also on the other node then it also becomes zombie. When the process is killed on one node then it becomes zombie, but on the other node it still works w/o problem. It seems it is hanged on some GFS2/DLM lock - see here. The problem is that when the process is killed (on any of the nodes) by SIGKILL (kill -9) it always becomes zombie, which can't be killed at all. Processes on both nodes use shared files on the GFS2 filesystem.

Testing is based on RHEL6 cluster, clvmd and GFS2. JBoss QA guys have the following problem when they are testing failover of HornetQ application. sys/kernel/debug/gfs2/jbm:jbm/glocks from both nodes +++ This bug was initially created as a clone of Bug #678585 +++

Dlm backup exec