NFS doesn't remount automatically after turn on or restart the NAS

[cc1]

Hi,

I added NFS with the GUI and it works, if I switch off or restart or unplug/plug again the network cable of the NAS , proxmox (4.4.19-1-pve) is not able to remount automatically the NFS and I need to do manually .

So I get this messagge on the log :

mount.nfs: Stale file handle

or the gui
"unable to activate storage 'NFS-Buffalo' - directory '/mnt/pve/NFS-Buffalo' does not exist (500)"

Manually - same result not working

mount -o remount /mnt/pve/NFS-Buffalo
mount.nfs: Stale file handle

Manually works

umount -f /mnt/pve/NFS-Buffalo
mount /mnt/pve/NFS-Buffalo

Any solution ?

 

[fabian]

this is to be expected with NFS - don't use NFS with servers that are not online 24/7

 

[cc1]

Hi @fabian ,

than you for your reply,
what system protocol do you suggest for a server ?

best

 

[Ashenafi]

Hi fabian,
I had the same problem on proxmox 3.4, after mounting
"unable to activate storage 'Backup' - directory '/mnt/pve/Backup' does not exist (500)"

 

[limone]

Just run this every minute via crontab:

#!/bin/bash
list=$(ls /mnt/pve)

for i in $list
do
        status=$(ls /mnt/pve/$i 2>&1)

        if [[ $status =~ .*Stale.* ]]
                then
                umount /mnt/pve/$i
        fi
done

The service "pvestatd" tries to remount every nfs share every 10 seconds automatically.

 

[scracha]

5 years later, still having to run hacks like the above & https://forum.proxmox.com/threads/m...oxmox-6-nfs-synology.56503/page-6#post-360230 Is there an alternative to NFS?

 

[OsvaldoP]

thanks a lot limone (2017)

Had the problem, unmount and wait solved the problem!!

 

[shalak]

@limone - the umount does the trick, but I'm worried about running this in crontab. Sometimes while this issue is happening, the `ls /mn/pve` appears to take forever. Did you ever have any issues with this?

 

[limone]

@limone - the umount does the trick, but I'm worried about running this in crontab. Sometimes while this issue is happening, the `ls /mn/pve` appears to take forever. Did you ever have any issues with this?

No, I'm not using NFS anymore.

 

[BassT]

No, I'm not using NFS anymore.

What u are use now?

 

[BobhWasatch]

The way to fix this is to use the automounter aka autofs. But the last time i tried to explain how to do that it was declared "too complicated" so you all can just google it or keep hacking away with cron and scripts.

 

[BassT]

I tryed the script, but

umount /mnt/pve/Backup
umount: /mnt/pve/Backup: not mounted

ls /mnt/pve
Backup  Proxmox-Server

 

[scracha]

With Proxmox 8 still throwing NFS errors, I've switched to CIFS. Zero issues.

 

[BassT]

With Proxmox 8 still throwing NFS errors, I've switched to CIFS. Zero issues.

But CIFS don't use rights on the files, so for Linux user not usable. For Windows ok, ...

 

[scracha]

But CIFS don't use rights on the files, so for Linux user not usable. For Windows ok, ...

My destination is a backup share on a Synology NAS so I'm not concerned. Easier NAT rule too.

 

[bbgeek17]

With Proxmox 8 still throwing NFS errors, I've switched to CIFS. Zero issues.

• NFS relies on maintaining file and mount handles for consistency, requiring a stable connection to preserve these handles.
• CIFS/SMB maintains a session-oriented connection that allows for the preservation of client states, such as authentication and file locks, even in the event of connection interruptions.

As such back to @fabian's comment from 2016:

this is to be expected with NFS - don't use NFS with servers that are not online 24/7

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox