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:
On a test client:
root@localhost:~# cat /etc/systemd/system/mnt-test.mount /etc/systemd/system/mnt-test.automount
[Unit]
Description=test mount
[Mount]
What=192.168.122.1:/test
Where=/mnt/test
Type=nfs4
Options=ro
TimeoutSec=10
[Install]
WantedBy=multi-user.target
[Unit]
Description=test automount
[Automount]
Where=/mnt/test
TimeoutIdleSec=10
[Install]
WantedBy=multi-user.target
With the server 192.168.122.1 powered off doing "/bin/ls -al /mnt/test" on the freshly rebooted client we see in the client logs:
Feb 4 12:15:48 localhost systemd: Got automount request for /mnt/test, triggered by 8729 (ls)
Feb 4 12:15:48 localhost systemd: Mounting test mount...
Feb 4 12:15:58 localhost systemd: mnt-test.mount mounting timed out. Stopping.
Feb 4 12:15:58 localhost systemd: Mounted test mount.
Feb 4 12:16:10 localhost systemd: Unmounting test mount...
Feb 4 12:16:10 localhost umount: umount: /mnt/test: target is busy.
Feb 4 12:16:10 localhost umount: (In some cases useful info about processes that use
Feb 4 12:16:10 localhost umount: the device is found by lsof(8) or fuser(1))
Feb 4 12:16:10 localhost systemd: mnt-test.mount mount process exited, code=exited status=32
Feb 4 12:16:10 localhost systemd: Unmounted test mount.
Feb 4 12:16:10 localhost systemd: Unit mnt-test.mount entered failed state.
Feb 4 12:16:10 localhost systemd: Failed to expire automount, ignoring: No such device
So "Mounted test mount" can't be correct and this seems to trigger unmounting attempt which should be not needed.
Version-Release number of selected component (if applicable):
systemd-219-62.el7_6.3.x86_64