Bug 2136046

Summary:	xfs_quota "cannot find mount point for path" error for an xfs volume mount not in the current search domain
Product:	Red Hat Enterprise Linux 8	Reporter:	bogdan.voaidas
Component:	xfsprogs	Assignee:	Pavel Reichl <preichl>
Status:	NEW ---	QA Contact:	Murphy Zhou <xzhou>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	esandeen, preichl, xzhou
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description bogdan.voaidas 2022-10-19 07:58:54 UTC

Description of problem:
I have 2 xfs volumes, one mounted with u+g quota and the other with u+g+p quota and some projects defined for the second volume.

Whenever I try to set or get report quota on the first volume mount (doesn't have project quota enabled and no projects defined anyway for this path) I get an error that 
"xfs_quota: cannot find mount point for path ..." for each project defined for the second volume.

## mount
/dev/mapper/lv_home on /export/home type xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,usrquota,grpquota)
/dev/mapper/lv_work on /export/work type xfs (rw,relatime,attr2,inode64,logbufs=8,logbsize=32k,usrquota,prjquota,grpquota)

# xfs_quota -xc report /export/home

xfs_quota: cannot find mount point for path `/export/work/_group/msg': No such file or file directory
xfs_quota: cannot find mount point for path `/export/work/_group/astroparticle': No such file or file directory
...

Version-Release number of selected component (if applicable): 5.0.0

Comment 2 Eric Sandeen 2023-04-24 22:04:29 UTC

moving this to xfsprogs, since xfs_quota is contained in that package, not the generic quota package.

Comment 3 Eric Sandeen 2023-07-18 01:53:02 UTC

The root cause here (IIRC) is that if you specify a specific mount point on the command line, it doesn't do a full scan of all mount points.

As a result when it later walks through the project quota list, it's unable to find the mount points associated with them if they aren't under the mount point specified - because they weren't scanned.

A workaround is probably to simply not specify the mount point, but we should find a way to fix this up.