- I have a NFS server (running OpenBSD, amd64, recent snapshots) at home.
- I have a laptop (also running OpenBSD, amd64, recent snapshots) which I like to connect to this server.
- Sometimes I like to close that laptop's lid to make it suspend.
- Closing the lid closes its connection to the network.
- On resume, I need to execute /etc/netstart to kick the NIC into action again.
- /etc/netstart sometimes does something that leads to it being stuck in the kernel (the NFS part of the kernel). It doesn't finish doing its job and it can't be killed.
- Shutting down the system doesn't work because the process won't end. This has once led to a panic (which I didn't record because I thought it happened because I was using a hard mount). The laptop needs to be forced off.
This seems like a bug to me. A painful one, because it can't be consistently reproduced and when it can it doesn't always lead to a panic. It's likely that I still can't post to the lists because I'm still on a DNSBL, so this isn't going to bugs@
I start nfsd with -tun 4. portmap and mountd are started without any special options; exports just allows access from the laptop.
I mount the directory with
# mount_nfs -s 10.0.1.1:/mnt/a /mnt/nfs_media
. I do this for a few different shares. All of the mounts are soft.
I use an USB NIC on the laptop (
axe(4), ASIX Electronics AX88772B).
Are there any other knobs which might help? Am I being silly and missing something obvious? Is the road to NFS fraught with peril?