Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
After trying an invalid mount option, other attempts to mount the file system hang.
Log messages from invalid mount option attempt:
May 6 13:32:06 tank-03 qarshd[10497]: Running cmdline: mount -t gfs2 -o garbage /dev/dm-5 /mnt/tank-cluster3
May 6 13:32:06 tank-03 kernel: GFS2: invalid mount option: garbage
May 6 13:32:06 tank-03 kernel: GFS2: can't parse mount arguments
May 6 13:32:06 tank-03 gfs_controld[9079]: do_leave: tank-cluster:tank-cluster3 not found
gfs_control ls output
- tank-03, where invalid option was attempted
name tank-cluster3
id 0x3bf37d95
flags 0x00000038 need_first,error,mounted
change member 3 joined 1 remove 0 failed 0 seq 3,3
members 1 3 4
- tank-01, first attempt after failure on tank-03
name tank-cluster3
id 0x3bf37d95
flags 0x00000025 need_first,blocked,join
change member 3 joined 1 remove 0 failed 0 seq 2,2
members 1 3 4
- tank-04, second attempt
name tank-cluster3
id 0x3bf37d95
flags 0x00000025 need_first,blocked,join
change member 3 joined 1 remove 0 failed 0 seq 1,1
members 1 3 4
Version-Release number of selected component (if applicable):
cman-3.0.9-5.el6.i686
gfs2-utils-3.0.9-5.el6.i686
kernel-2.6.32-23.el6.i686
How reproducible:
Easily
Steps to Reproduce:
1. mount -o foo /dev/... /mnt/...
2. check for "gfs_controld do_leave: $cluster:$locktable not found" in /var/log/cluster/gfs_controld.log
Actual results:
Expected results:
Additional info:
*** Bug 580940 has been marked as a duplicate of this bug. ***
Comment 10releng-rhel@redhat.com
2010-07-02 18:55:02 UTC
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.