Hya

System
Several Debian stretch's amd64.
One of them is a nfs server for other ones.

What I did
One laptop is connected to this system via eth0, then common drive is nfs mounted.
... did some jobs (mostly reading)...
The laptop is disconnected from this system. (I did not unmount the nfs drive).
... did more jobs (not networked) ...
Then at the end of the day, when I tried to shutdown the laptop, systemd waits forever to take care of nfs drive.


What I tried
I was unable to log in through tty2, (of course not.)
Network was not active, so that no ssh log in.
No way to cancel the shutdown process.

Power button long press did power-off.

Question
What is the correct way to get out of this situation?
Is there anything like systemd force time out?

Yes, I know I did wrong thing to run into this situation. But it was too late when I realized.

++ added on edit.
This thread suggests to use debug shell. But it was not active either!

Yes, systemd.automount should work for you.

https://wiki.archlinux.org/index.php/fstab
https://wiki.archlinux.org/index.php/NFS

AFAIK, there is no solution to this problem. I think it's a known bug with systemd which they will not fix. It's even worse if you're connected by wifi, because the wifi connection will invariably be shut down before systemd attempts to shut down nfs. So, you always get the stupid nfs mount hang. Every. Single. Time. And they're uninterested in fixing this bug.

The only solution I've managed is to remember to manually umount nfs shares before shutting down the computer. If I really wanted to get fancy, I could try and figure out a script which automatically runs before logging out that umounts nfs shares first.

Hya

Thanks for posts.

Yes, systemd.automount works. (shutdown after eth0 disconnect without unmounting nfs)

It looks like that there is no way to get out, once we run into this trouble.

cheers

Hya

With systemd.automount, everytime nfs drive is accessed, penguin waits for timeout, when nfs drive is unavailable.

A kind of side effect.

cheers

Thread back to unsolved.

There is a device-timeout option that you can add in fstab to set the time it waits but that is the way it works.

Hya

Thanks for your reply.

Yes, I agree, that is a timeout option. I need to adjust many options, I guess.

cheers