Loss of network connection causes major shutdown problem and reboot delays

I am running 42.2 with KDE desktop and Wicked network service.

I have recently had a serious (time wasting) problem which appears to have been result of disconnection of network devices and in particular a NAS device which had an NFS share.

Following the proper (from control page) shutting down of the NAS box to allow it to be moved, my desktop froze. (OK I did not close the NFS connection in Yast but situation was at worst no different from a cable disconnection) I was only able to get back some control from a Ctrl-Alt-Del which allowed me to log out but after logging back in desktop was still frozen.

Tried to reboot instead of logout and reboot process stalled.

I was only able to recover using Alt-SysReq and REISUB and only the U and B gave me any result. It appears the other functions are now locked out.

On restarting I had to wait for several 4 min plus delays because the NFS connection could not be made.

It appears that the network wait delays need setting adjusting (is this possible) but also that there is no robustness in the system following a network disconnection. Are there some defaults I should be adjusting to avoid this problem?

Budge

The mistake you made was not unmounting the share from the client(s) first. The use of autofs can help with minimising this kind of behaviour, protecting client systems from server failure by mounting the NFS filesystems only while they are required, and automatically unmounting when not required after a configurable timeout period.

An openSUSE guide for ‘on-demand’ mounting with autofs…

https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.autofs.html#sec.autofs.nfs