You are not logged in.
I woke up today to see some of my docker containers in unhealty/exited state. Tried to debug the problem for a while, then I realized nfs mounts have stopped working and these containers had some folders from that mounted. I restarted the nfs-server.service and everything was fine again. Went around to see why that happened, expecting some error message but the logs seem like I just stopped the service normally. How can I start debugging this problem?
Here is the relevant part of logs:
Jan 31 13:46:00 arch-pi systemd[1]: Starting NFS server and services...
Jan 31 13:46:00 arch-pi exportfs[555]: exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "192.168.1.0/24:/srv/nfs/data".
Jan 31 13:46:00 arch-pi exportfs[555]: Assuming default behaviour ('no_subtree_check').
Jan 31 13:46:00 arch-pi exportfs[555]: NOTE: this default has changed since nfs-utils version 1.0.x
Jan 31 13:46:00 arch-pi exportfs[555]: exportfs: /etc/exports [2]: Neither 'subtree_check' or 'no_subtree_check' specified for export "192.168.1.0/24:/srv/nfs/archive".
Jan 31 13:46:00 arch-pi exportfs[555]: Assuming default behaviour ('no_subtree_check').
Jan 31 13:46:00 arch-pi exportfs[555]: NOTE: this default has changed since nfs-utils version 1.0.x
Jan 31 13:46:00 arch-pi exportfs[555]: exportfs: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export "192.168.1.0/24:/srv/nfs/samples".
Jan 31 13:46:00 arch-pi exportfs[555]: Assuming default behaviour ('no_subtree_check').
Jan 31 13:46:00 arch-pi exportfs[555]: NOTE: this default has changed since nfs-utils version 1.0.x
Jan 31 13:46:00 arch-pi exportfs[555]: exportfs: /etc/exports [4]: Neither 'subtree_check' or 'no_subtree_check' specified for export "192.168.1.0/24:/srv/nfs/1tb".
Jan 31 13:46:00 arch-pi exportfs[555]: Assuming default behaviour ('no_subtree_check').
Jan 31 13:46:00 arch-pi exportfs[555]: NOTE: this default has changed since nfs-utils version 1.0.x
Jan 31 13:46:00 arch-pi rpc.nfsd[557]: rpc.nfsd: Unable to request RDMA services: Protocol not supported
Jan 31 13:46:00 arch-pi systemd[1]: Finished NFS server and services.
Feb 01 02:05:44 arch-pi systemd[1]: Stopping NFS server and services...
Feb 01 02:05:44 arch-pi systemd[1]: nfs-server.service: Deactivated successfully.
Feb 01 02:05:44 arch-pi systemd[1]: Stopped NFS server and services.`
It was stopped at around 2 am, I was fast asleep by 11 pm.
Offline
There was a problem with one of the shared USB drives. It was unmounted and remounted as read-only, and that somehow caused the nfs server to be completely stopped. Can I prevent these types of failures from stopping the nfs-server,service? There are 3 other shares that were working perfectly fine.
Offline
There was a problem with one of the shared USB drives. It was unmounted and remounted as read-only
There's a lot of issues about chips used in USB 3.0 enclosures for which Linux uses UAS, look for UAS quirks (eg.: https://en.opensuse.org/SDB:USB_3.0_Har … eshooting)
<49,17,III,I> Fama di loro il mondo esser non lassa;
<50,17,III,I> misericordia e giustizia li sdegna:
<51,17,III,I> non ragioniam di lor, ma guarda e passa.
Offline
Not sure whether you can prevent the service from stopping when the exported FS disappears, but you could auto-restart it w/ RestartSec= and Restart=
https://man.archlinux.org/man/core/syst … en#OPTIONS
https://wiki.archlinux.org/title/System … unit_files
Offline
Not sure whether you can prevent the service from stopping when the exported FS disappears, but you could auto-restart it w/ RestartSec= and Restart=
https://man.archlinux.org/man/core/syst … en#OPTIONS
https://wiki.archlinux.org/title/System … unit_files
Dunno if this could be somewhat realted, but:
mountpoint=path
mp
This option makes it possible to only export a directory if it has successfully been mounted. If no path is given (e.g. mountpoint or mp) then the export point must also be a mount point. If it isn't then the export point is not exported. This allows you to be sure that the directory underneath a mountpoint will never be exported by accident if, for example, the filesystem failed to mount due to a disc error.If a path is given (e.g. mountpoint=/path or mp=/path) then the nominated path must be a mountpoint for the exportpoint to be exported.
<49,17,III,I> Fama di loro il mondo esser non lassa;
<50,17,III,I> misericordia e giustizia li sdegna:
<51,17,III,I> non ragioniam di lor, ma guarda e passa.
Offline