Problems with NFS after rebooting OMV5

  • 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.

  • I'd recommend a better title for the post mentioning NFS

    omv 6.9.6-2 (Shaitan) on RPi CM4/4GB with 64bit Kernel 6.1.21-v8+

    2x 6TB 3.5'' HDDs (CMR) formatted with ext4 via 2port PCIe SATA card with ASM1061R chipset providing hardware supported RAID1


    omv 6.9.3-1 (Shaitan) on RPi4/4GB with 32bit Kernel 5.10.63 and WittyPi 3 V2 RTC HAT

    2x 3TB 3.5'' HDDs (CMR) formatted with ext4 in Icy Box IB-RD3662-C31 / hardware supported RAID1

    For Read/Write performance of SMB shares hosted on this hardware see forum here

  • zeitalexgithub

    Changed the title of the thread from “Rebooting RPi4 with OMV5” to “Problems with NFS after rebooting OMV5”.
    • Official Post

    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.

    omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    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.

    omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    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.

    omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post

    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.

    omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!