If I have to reboot my RPi4 with OMV5 on it, then I also have to reboot all NFS clients, otherwise NFS share becomes not accessible. Any help would be highly appreciated.
Problems with NFS after rebooting OMV5
-
-
I'd recommend a better title for the post mentioning NFS
-
zeitalexgithub
Hat den Titel des Themas von „Rebooting RPi4 with OMV5“ zu „Problems with NFS after rebooting OMV5“ geändert. -
I also have to reboot all NFS clients,
That would be an issue with the nfs client and the settings they are using. If the client is hard mounting an nfs share and has a timeout longer than the rpi takes to reboot, it shouldn't be transparent. Not much can be done on the OMV side to fix that.
-
-
Thanks a lot for your answers. What nfs mount options would you suggest on linux client?
-
What nfs mount options would you suggest on linux client?
With Ubuntu 20.04 clients, I actually just use "defaults" since that includes rw and hard.
-
i am also using defaults on Lubuntu 20.04. What would you suggest to avoid powering off / rebooting all clients on OMV reboot/power off?
-
-
What would you suggest to avoid powering off / rebooting all clients on OMV reboot/power off?
It depends on what those clients are doing. If they have locks on files on nfs when the nfs server is rebooted, the program creating the lock may not like that. If the clients just have the shares mounted, rebooting the server shouldn't cause any problems.
-
There are no locks. The client mounts nfs share via fstab.
-
The client mounts nfs share via fstab.
Then you shouldn't have any issue when rebooting the server and not rebooting the client. I do that often. I even used to reboot my nfs server while Proxmox VMs had ISOs on it attached. Never had issues.
-
-
Maybe try autofs?
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!