[systemd-devel] process hangs on mount with automount unit with TimeoutIdleSec

[Igor Bukanov]

Hi,

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
the host.

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.

Is it a known bug? During that hang  `systemctl status
mount-pint-unit-file.mount` shows:

  Active: failed (Result: exit-code) since Tue 2015-12-01 11:56:09
CET; 21min ago
  Process: 1483 ExecMount=/usr/bin/mount ...  (code=exited, status=1/FAILURE)

Dec 01 11:56:09 untrusted mount[1483]: read: Connection reset by peer
Dec 01 11:56:09 untrusted systemd[1]: xyz.mount: Mount proc...=1
Dec 01 11:56:09 untrusted systemd[1]: xyz.mount: Unit enter...e.
Dec 01 11:56:42 untrusted systemd[1]: Unmounted /xyz.

systemctl status mount-pint-unit-file.automount gives active (running)