Update of the information about this problem.<br>
<br>
We see that the loop that causes
the overload of "dlm" is:<br>
<br>
<ol><li>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 element.</li><li>Node 3 replies "the owner of this element is now the node 4".</li><li>Node 1 sends a "request" message to node 4.</li><li>Node 4 replies "I have not it" (error code EBADR = -53).</li>
<li>goto step 1</li></ol>
<p>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<br>
</p>
<p>Kind regards.</p>