Red Hat Bugzilla – Bug 1288519
process hangs on mount with automount unit with TimeoutIdleSec
Last modified: 2016-12-20 11:37:37 EST
I have an automount unit that mounts sshfs filesystem via
corresponding mount unit. Without recently introduced TimeoutIdleSec
in [Automount] this works as expected even when ssh cannot connect to
For example, if I disconnect the network and try to `ls mount-point`,
I get expected:
ls: cannot open directory /set/kino: No such device
If I restore the network, the directory is mounted and ls shows its context.
However, if under systemd 222 under Fedora 23 I add TimeoutIdleSec=30
to the automount unit, reboot the system and disconnect network, then
as before `ls mount-point` shows the same error. But when I restore
network and try `ls mount-point`, the `ls` process just hangs. It
cannot be killed even with kill -9. Running `systemctl restart
mount-pint-unit-file.mount` makes ls to terminate.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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
Thank you for reporting this bug and we are sorry it could not be fixed.