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:
quota -u user reports wrong path information for automounted directories
Version-Release number of selected component (if applicable):
client
# rpm -qa|grep quota|sort
quota-4.01-17.el7.x86_64
quota-doc-4.01-17.el7.noarch
quota-nld-4.01-17.el7.x86_64
quota-nls-4.01-17.el7.noarch
server
nfs-utils-1.3.0-0.54.el7.x86_64
quota-4.01-17.el7.x86_64
quota-doc-4.01-17.el7.noarch
quota-nld-4.01-17.el7.x86_64
quota-nls-4.01-17.el7.noarch
xfsprogs-4.5.0-15.el7.x86_64
# mount|grep storage
/dev/mapper/storage_fs4-storage on /storage type xfs (rw,relatime,seclabel,attr2,inode64,sunit=512,swidth=512,usrquota,grpquota)
# xfs_info /storage
meta-data=/dev/mapper/storage_fs4-storage isize=512 agcount=32, agsize=152596480 blks
= sectsz=4096 attr=2, projid32bit=1
= crc=1 finobt=0 spinodes=0
data = bsize=4096 blocks=4883086336, imaxpct=5
= sunit=64 swidth=64 blks
naming =version 2 bsize=4096 ascii-ci=0 ftype=1
log =internal bsize=4096 blocks=521728, version=2
= sectsz=4096 sunit=1 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
How reproducible:
Always.
Steps to Reproduce:
1.
# ls /home/user1 /home/user2
The home directories with quotas enabled are automounted now (via autofs with sssd backend and quota maps in LDAP directory).
2.
# quota -u user1
# quota -u user2
3.
Actual results:
Disk quotas for user user1 (uid 1001):
Filesystem blocks quota limit grace files quota limit grace
fs4:/storage/home/user1
... correct values for user1 ...
Disk quotas for user user2 (uid 1002):
Filesystem blocks quota limit grace files quota limit grace
fs4:/storage/home/user1 (<---!!!!)
... correct values for user2 ...
Expected results:
Disk quotas for user user1 (uid 1001): (see above)
Disk quotas for user user2 (uid 1002):
Filesystem blocks quota limit grace files quota limit grace
fs4:/storage/home/user2
... correct values for user2 ...
Additional info:
It is only the path fs4:/storage/home/... which is wrong here.
Quota seems to report the path of the directory which has been mounted first (maybe of /etc/mtab). The quota values itself are correct.
The bug already exists in RedHat 6.9 (quota-3.17-23.el6.x86_64).
Description of problem: quota -u user reports wrong path information for automounted directories Version-Release number of selected component (if applicable): client # rpm -qa|grep quota|sort quota-4.01-17.el7.x86_64 quota-doc-4.01-17.el7.noarch quota-nld-4.01-17.el7.x86_64 quota-nls-4.01-17.el7.noarch server nfs-utils-1.3.0-0.54.el7.x86_64 quota-4.01-17.el7.x86_64 quota-doc-4.01-17.el7.noarch quota-nld-4.01-17.el7.x86_64 quota-nls-4.01-17.el7.noarch xfsprogs-4.5.0-15.el7.x86_64 # mount|grep storage /dev/mapper/storage_fs4-storage on /storage type xfs (rw,relatime,seclabel,attr2,inode64,sunit=512,swidth=512,usrquota,grpquota) # xfs_info /storage meta-data=/dev/mapper/storage_fs4-storage isize=512 agcount=32, agsize=152596480 blks = sectsz=4096 attr=2, projid32bit=1 = crc=1 finobt=0 spinodes=0 data = bsize=4096 blocks=4883086336, imaxpct=5 = sunit=64 swidth=64 blks naming =version 2 bsize=4096 ascii-ci=0 ftype=1 log =internal bsize=4096 blocks=521728, version=2 = sectsz=4096 sunit=1 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 How reproducible: Always. Steps to Reproduce: 1. # ls /home/user1 /home/user2 The home directories with quotas enabled are automounted now (via autofs with sssd backend and quota maps in LDAP directory). 2. # quota -u user1 # quota -u user2 3. Actual results: Disk quotas for user user1 (uid 1001): Filesystem blocks quota limit grace files quota limit grace fs4:/storage/home/user1 ... correct values for user1 ... Disk quotas for user user2 (uid 1002): Filesystem blocks quota limit grace files quota limit grace fs4:/storage/home/user1 (<---!!!!) ... correct values for user2 ... Expected results: Disk quotas for user user1 (uid 1001): (see above) Disk quotas for user user2 (uid 1002): Filesystem blocks quota limit grace files quota limit grace fs4:/storage/home/user2 ... correct values for user2 ... Additional info: It is only the path fs4:/storage/home/... which is wrong here. Quota seems to report the path of the directory which has been mounted first (maybe of /etc/mtab). The quota values itself are correct. The bug already exists in RedHat 6.9 (quota-3.17-23.el6.x86_64).