Bug 1488490

Summary:	fuser gets confused by multiple mounts from the same NFS server
Product:	[Fedora] Fedora	Reporter:	Marius Vollmer <mvollmer>
Component:	psmisc	Assignee:	Jaromír Cápík <jaromir.capik>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	26	CC:	fedora, jaromir.capik, jrybar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-29 11:24:13 UTC	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 Marius Vollmer 2017-09-05 14:03:10 UTC

Description of problem:

If there are multiple mounts from a single NFS server, "fuser -m" can't seem to differentiate between them.  If one of them has files open, fuser shows all of them as having files open.

Version-Release number of selected component (if applicable):
psmisc-22.21-9.fc26.x86_64

How reproducible:
Always

Steps to Reproduce:
1. mount 192.168.100.1:/home/mvo /home/mvo
2. mount 192.168.100.1:/home/foo /home/foo
3. cd /home/mvo/work/cockpit
4. echo $$
17400
4. fuser -m /home/mvo
/home/mvo:           17400c
5. fuser -m /home/foo
/home/foo:           17400c
6. lsof /home/mvo

Actual results:
fuser reports /home/foo to be in use for the current directory of the shell, but that shell has its cwd in /home/mvo/

Expected results:
fuser reports /home/foo as unused.

Additional info:
lsof gets this right:

# lsof /home/mvo
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF    NODE NAME
bash    17400 root  cwd    DIR   0,46    36864 5570718 /home/mvo/work/cockpit/test/verify (192.168.100.1:/home/mvo)
lsof    17679 root  cwd    DIR   0,46    36864 5570718 /home/mvo/work/cockpit/test/verify (192.168.100.1:/home/mvo)
lsof    17680 root  cwd    DIR   0,46    36864 5570718 /home/mvo/work/cockpit/test/verify (192.168.100.1:/home/mvo)
# lsof /home/foo
<empty>

Comment 1 Fedora End Of Life 2018-05-03 07:59:22 UTC

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2018-05-29 11:24:13 UTC

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.