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.

Bug 749434

Summary: [xfs/xfstests 261] xfs_quota exits immediately if bogus entry is in mtab
Product: Red Hat Enterprise Linux 6 Reporter: Eryu Guan <eguan>
Component: xfsprogsAssignee: Eric Sandeen <esandeen>
Status: CLOSED ERRATA QA Contact: Branislav NĂ¡ter <bnater>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.3CC: bnater, branto, psplicha, rwheeler
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: xfsprogs-3.1.1-7.el6 Doc Type: Bug Fix
Doc Text:
No Documentation needed (not customer reported)
Story Points: ---
Clone Of:
: 756363 (view as bug list) Environment:
Last Closed: 2012-06-20 14:11:06 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:    
Bug Blocks: 756363    

Description Eryu Guan 2011-10-27 03:10:58 UTC
Description of problem:
xfstests 261 fails on xfs, the description is from 261

# This test exercises an issue in libxcmd where a problem with any
# mount point or project quota directory causes the program to exit
# complete.  The effect of this is that one cannot operate on any
# directory, even if the problem directory is completely unrelated
# to the directory one wants to operate on.

Version-Release number of selected component (if applicable):
xfsprogs-3.1.1-6.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. check 261
2.
3.
  
Actual results:
261 fail, or reproduce it manually
# cat testmount
/dev/sda5 /mnt/tests xfs rw,seclabel,relatime,attr2,delaylog,noquota 0 0
/dev/sda9 /tmp/nosuchdir xfs rw 0 0
# xfs_quota -t testmount
xfs_quota: cannot initialise path table: No such file or directory

xfs_quota exits even if there is a valid entry for /dev/sda5

Expected results:


Additional info:

Comment 2 Eric Sandeen 2011-10-28 15:43:54 UTC
6bca0145 upstream fixes this, with some prerequisites.

Comment 9 Eric Sandeen 2012-02-22 16:38:25 UTC
Built & tagged in xfsprogs-3.1.1-7.el6

Comment 11 Eric Sandeen 2012-04-25 21:09:23 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:
No Documentation needed (not customer reported)

Comment 13 errata-xmlrpc 2012-06-20 14:11:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0883.html