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.
DescriptionStrahil Nikolov
2017-07-28 11:30:39 UTC
Description of problem:
x-systemd.idle-timeout does not dismount the file system
Version-Release number of selected component (if applicable):
systemd-libs-219-30.el7_3.9.x86_64
systemd-sysv-219-30.el7_3.9.x86_64
systemd-python-219-30.el7_3.9.x86_64
systemd-219-30.el7_3.9.x86_64
How reproducible:
Always
Steps to Reproduce:
1.Set an fstab entry:
/dev/vdb1 /mnt xfs defaults,x-systemd.automount,x-systemd.idle-timeout=1min 0 0
2.Reboot to test if the mount target will be brought online after a reboot
3.Check the filesystem is mounted and the timeout value of the monitoring service:
# findmnt /mnt
TARGET SOURCE FSTYPE OPTIONS
/mnt systemd-1 autofs rw,relatime,fd=36,pgrp=1,timeout=300,minproto=5,maxproto=5,direct
/mnt /dev/vdb1 xfs rw,relatime,seclabel,attr2,inode64,noquota
Actual results:
Mount point is mounted on boot , but never dismounted (while it\s not used at all).
Expected results:
The "timeout=" parameter should be set to "60" and the mount point should be dismounted after 60 seconds.
Additional info:
The time out option in Fedora 25 /with systemd-231-17.fc25.x86_64 / is working as expected.