Description of problem: The mount command hangs when a node tries to mount a GFS file system without using the "hostdata=nodir=1" option when the file system is already mounted on other nodes using the "hostdata=nodir=1" option. Version-Release number of selected component (if applicable): kmod-gfs-0.1.1-8.2.6.17_1.2519.4.14.el5 cman-2.0.12-1.fc6 How reproducible: 100% Steps to Reproduce: 1. mount file system with "hostdata=nodir=1" on one node 2. mount file system without above option on another node Actual results: I had the file system mounted on two nodes when I tried to mount the file system on a third without the above option. The mount hung. Kernel messages: -- morph-01 (mounted nodir=1) dlm: morph-cluster0: recover 5 dlm: morph-cluster0: add member 3 dlm: morph-cluster0: config mismatch: 32,1 nodeid 3: 32,0 dlm: morph-cluster0: ping_members aborted -22 last nodeid 3 dlm: morph-cluster0: total members 3 error -22 dlm: morph-cluster0: recover_members failed -22 dlm: morph-cluster0: recover 5 error -22 -- morph-02 (mounted nodir=1) dlm: morph-cluster0: recover 3 dlm: morph-cluster0: add member 3 dlm: morph-cluster0: config mismatch: 32,1 nodeid 3: 32,0 dlm: morph-cluster0: ping_members aborted -22 last nodeid 3 dlm: morph-cluster0: total members 3 error -22 dlm: morph-cluster0: recover_members failed -22 dlm: morph-cluster0: recover 3 error -22 -- morph-03 (attempted mount) Trying to join cluster "lock_dlm", "morph-cluster:morph-cluster0" dlm: morph-cluster0: recover 1 dlm: morph-cluster0: add member 2 dlm: morph-cluster0: add member 1 dlm: morph-cluster0: add member 3 dlm: morph-cluster0: config mismatch: 32,0 nodeid 1: 32,1 Joined cluster. Now mounting FS... dlm: morph-cluster0: ping_members aborted -22 last nodeid 1 dlm: morph-cluster0: total members 3 error -22 dlm: morph-cluster0: recover_members failed -22 dlm: morph-cluster0: recover 1 error -22 Expected results: mount command should fail with an error that the nodir=1 option is required. Additional info:
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
patch posted to rhkernel http://post-office.corp.redhat.com/archives/rhkernel-list/2007-May/msg00713.html
patch reposted to rhkernel http://post-office.corp.redhat.com/archives/rhkernel-list/2007-June/msg01066.html
in 2.6.18-24.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5
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 the 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/RHBA-2007-0959.html