Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 635023

Summary: Better error reporting when mounting a gfs fs without enough journals
Product: Red Hat Enterprise Linux 5 Reporter: Abhijith Das <adas>
Component: gfs-kmodAssignee: Abhijith Das <adas>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: low Docs Contact:
Priority: low    
Version: 5.6CC: bmarzins, edamato, iannis, james.brown, rpeterso, ssaha, swhiteho
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: gfs-kmod-0.1.34-14.el5 Doc Type: Bug Fix
Doc Text:
When a Global File System (GFS) does not have enough journals, an attempt to mount it can fail, and an error message is written to standard error. However, this message was not very informative, and did not include important information required to determine the cause of the problem. With this update, the kernel now returns the "-EUSERS" error code, which allows the mount.gfs utility to recognize this error, and display more informative message.
Story Points: ---
Clone Of: 537201 Environment:
Last Closed: 2011-01-13 23:22:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 537201    
Bug Blocks: 600387, 600408    

Comment 1 RHEL Program Management 2010-09-17 16:17:31 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 2 Robert Peterson 2010-09-20 18:15:10 UTC
Build 2771460 successful.  Changing status to Modified.
This fix is in gfs-kmod-0.1.34-14.el5.

Comment 4 RHEL Program Management 2010-09-21 05:46:51 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 6 Jaromir Hradilek 2010-12-01 14:52:59 UTC
    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:
When a Global File System (GFS) does not have enough journals, an attempt to mount it can fail, and an error message is written to standard error. However, this message was not very informative, and did not include important information required to determine the cause of the problem. With this update, the kernel now returns the "-EUSERS" error code, which allows the mount.gfs utility to recognize this error, and display more informative message.

Comment 7 Nate Straz 2010-12-06 15:01:55 UTC
Verified against gfs2-utils-0.1.62-28.el5

[root@dash-03 ~]# mount /dev/dash/grow /mnt/grow
/sbin/mount.gfs2: Too many nodes mounting filesystem, no free journals

Comment 9 errata-xmlrpc 2011-01-13 23:22:16 UTC
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/RHBA-2011-0089.html