This bug has been copied from bug #504188 and has been proposed to be backported to 5.5 z-stream (EUS).
in kernel 2.6.18-194.20.1.el5 linux-2.6-fs-dlm-fix-try-1cb-failure-part-2.patch linux-2.6-fs-dlm-no-node-callback-when-try-1cb-lock-req-fails.patch
Confirmed patches listed in comment 4 are applied in kernel 2.6.18-194.26.1.el5 correctly. Set SanityOnly verified.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0839.html
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: In a two node cluster, the lock master of two folders can move 100 files from one folder to the other in less than 1 second. If a server is not the lock master for that folder, it would take that server 3-5 seconds to perform the same task on GFS1 (Global File System 1), and 30-50 seconds on GFS2 (Global File System 2). With this update, the aforementioned task takes less than 1 second on GFS1 and about 3 seconds on GFS2.