Bug 1476234 - x-systemd.idle-timeout not working in fstab
x-systemd.idle-timeout not working in fstab
Status: CLOSED DUPLICATE of bug 1354410
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: systemd (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: rc
: ---
Assigned To: systemd-maint
Depends On:
  Show dependency treegraph
Reported: 2017-07-28 07:30 EDT by Strahil Nikolov
Modified: 2018-06-22 07:22 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-06-22 07:22:19 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Strahil Nikolov 2017-07-28 07:30:39 EDT
Description of problem:
x-systemd.idle-timeout does not dismount the file system

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

How reproducible:

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
/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.
Comment 3 Strahil Nikolov 2017-07-30 15:27:46 EDT
If systemd v220 supports it correctly , then this should be marked as duplicate and closed ...
Comment 4 David Tardon 2018-06-22 07:22:19 EDT

*** This bug has been marked as a duplicate of bug 1354410 ***

Note You need to log in before you can comment on or make changes to this bug.