[Linux-cluster] Cluster failure, dlm overload

wsfax alu.es wsfax.alu.es at gmail.com
Wed Apr 11 15:17:29 UTC 2012

Update of the information about this problem.

We see that the loop that causes the overload of "dlm" is:

   1. Node 1 sends a "lookup" message, related to some filesystem and
   inode, to the master node (node 3), asking for the current owner of this
   2. Node 3 replies "the owner of this element is now the node 4".
   3. Node 1 sends a "request" message to node 4.
   4. Node 4 replies "I have not it" (error code EBADR = -53).
   5. goto step 1

This loop appends several hundreds per seconds, multiplied by all
filesystem and inodes with this problem. In total, several tenths of
thousands messages in DLM, until restart of the cluster

Kind regards.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20120411/0e8fec16/attachment.htm>

More information about the Linux-cluster mailing list