[SOLVED] NFS share inconsistency between nodes

[CZappe]

I just configured a new PVE node (v 7.4-17) in our existing environment and have added several NFS shares to Datacenter>Storage that we use to host production disk images and VZDump files. The NFS shares populate under the new node, as expected and show the correct storage usage that our other nodes report. However, when I attempt to dig deeper and view the list of Backups and VM Disks in the GUI, the new node shows no files.



When I SSH into the new node, I can navigate to the NFS share located at /mnt/pve/qnap1v1 and notice that the contents of the NFS share is different, as well, and that the images and dump folders are empty

NEW SERVER:
root@tsoukalos:/mnt/pve/qnap1v1# ll
total 12
drwxr-xr-x 2 root root 4096 Oct 24 16:57 dump
drwxr-xr-x 2 root root 4096 Oct 24 16:57 images
drwxrwxrwx 3 root root 4096 Jan 10  2022 @Recycle
root@tsoukalos:/mnt/pve/qnap1v1# ll images/
total 0

EXISTING SERVER:
root@hera:/mnt/pve/qnap1v1# ll
total 84
drwxr-xr-x  8 root root 53248 Oct 25 06:45 dump
drwxr-xr-x 18 root root  4096 Oct 17 11:48 images
-rw-r--r--  1 root root   146 Jan  5  2022 MegaSAS.log
drwxr-xr-x  4 root root  4096 Mar 16  2023 moths
drwxr-xr-x  2 root root  4096 Apr 17  2020 private
drwxrwxrwx  3 root root  4096 Nov  9  2022 @Recycle
drwxr-xr-x  4 root root  4096 Aug  5  2015 template
drwxr-xr-x  3 root root  4096 Oct 25 10:38 xfer
root@hera:/mnt/pve/qnap1v1# ll images/
total 64
drwxr----- 2 root root 4096 Jun 16 22:02 117
drwxr-xr-x 2 root root 4096 Dec 21  2020 119
drwxr----- 2 root root 4096 Dec 28  2022 140
drwxr----- 2 root root 4096 Jun  8 21:33 170
drwxr----- 2 root root 4096 Oct  5  2021 196
drwxr----- 2 root root 4096 Apr 10  2023 198
drwxr----- 2 root root 4096 Jan 13  2023 210
drwxr----- 2 root root 4096 Jan 13  2023 211
drwxr----- 2 root root 4096 Jan 13  2023 212
drwxr----- 2 root root 4096 Jan 20  2023 213
drwxr----- 2 root root 4096 Jan 13  2023 214
drwxr----- 2 root root 4096 Jun  6 13:09 215
drwxr----- 2 root root 4096 Aug 12 11:18 250
drwxr----- 2 root root 4096 Aug 18 14:25 275
drwxr----- 2 root root 4096 Mar 16  2023 555
drwxr----- 2 root root 4096 Mar 31  2023 778

Not sure what would cause this new node to nominally mount the NFS share but not actually "see" it. Is there an additional configuration that I can check to make sure that the new node can access files on this share correctly?

 

[bbgeek17]

Not sure what would cause this new node to nominally mount the NFS share but not actually "see" it. Is there an additional configuration that I can check to make sure that the new node can access files on this share correctly?

The most likely explanation is that you misconfigured something or made a typo.
The context is different, the dates are different.
Check the context of /etc/pve/storage.cfg
Execute "mount" and compare the NFS paths
Run "showmount -a nfs_server" - are the hosts mounting same exports?

---

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

 

[CZappe]

The most likely explanation is that you misconfigured something or made a typo.
The context is different, the dates are different.
Check the context of /etc/pve/storage.cfg

Yep, that was it. I had mapped the wrong mount point, "Public"

nfs: qnap1v1
        export /Public
        path /mnt/pve/qnap1v1
        server 192.168.XX.XX
        content backup,images
        options vers=3
        prune-backups keep-daily=3,keep-monthly=1,keep-weekly=2

I trashed the bad NFS share and re-added it with the correct mount point. Success!

Thank you, very much.