Hello forum,
I've got this issue between 2 proxmox servers (v4 and v5, both up-to-date, both physical machines connected by a switch).
Both machines can ping each-other and their IP and hostname are present into the /etc/hosts of the other machine.
I used this simple method that worked well a few years ago but now I get a "NFS Shares: storage is not online (500)" by configuring the nfs storage of the client machine.
On the server machine:
# ls -l /home/
drwxr-xr-x 6 root root 4096 déc. 27 20:54 nfs <= that is the shared folder
/etc/exports:
/home/nfs 192.168.20.132(rw,sync,no_subtree_check) <= the IP of a "test-client" fedora
/home/nfs 192.168.20.150(rw,sync,no_subtree_check) <= the IP of the proxmox client
/home/nfs 192.168.20.160(rw,sync,no_subtree_check) <= the IP of the proxmox server itself (for tests)
/etc/hosts.allow and /etc/hosts.deny are empty.
On the proxmox client machine:
# cat /etc/pve/storage.cfg
nfs: nfs_proxmox
export /home/nfs
path /mnt/pve/nfs_proxmox
server 192.168.20.160 <= the IP of the proxmox nfs server
content vztmpl,iso,rootdir,images,backup
maxfiles 20
options vers=3
# mount -t nfs 192.168.20.160:/home/nfs /mnt/proxmox-asrock
gets in time-out.
# showmount -e 192.168.20.160
Export list for 192.168.20.160:
/home/nfs 192.168.20.160,192.168.20.132,192.168.20.150
This result is correct, but I'm very surprised that it takes more than 1 min. to get it.
From the fedora test client: it is the same: mounting gets in time out.
From the proxmox server itself: the nfs connection on itself works good and immediately => I assume that /etc/export is correct.
Does somebody has got an idea where the issue could come from?
Thanks in advance.
Regards
Arnaud
I've got this issue between 2 proxmox servers (v4 and v5, both up-to-date, both physical machines connected by a switch).
Both machines can ping each-other and their IP and hostname are present into the /etc/hosts of the other machine.
I used this simple method that worked well a few years ago but now I get a "NFS Shares: storage is not online (500)" by configuring the nfs storage of the client machine.
On the server machine:
# ls -l /home/
drwxr-xr-x 6 root root 4096 déc. 27 20:54 nfs <= that is the shared folder
/etc/exports:
/home/nfs 192.168.20.132(rw,sync,no_subtree_check) <= the IP of a "test-client" fedora
/home/nfs 192.168.20.150(rw,sync,no_subtree_check) <= the IP of the proxmox client
/home/nfs 192.168.20.160(rw,sync,no_subtree_check) <= the IP of the proxmox server itself (for tests)
/etc/hosts.allow and /etc/hosts.deny are empty.
On the proxmox client machine:
# cat /etc/pve/storage.cfg
nfs: nfs_proxmox
export /home/nfs
path /mnt/pve/nfs_proxmox
server 192.168.20.160 <= the IP of the proxmox nfs server
content vztmpl,iso,rootdir,images,backup
maxfiles 20
options vers=3
# mount -t nfs 192.168.20.160:/home/nfs /mnt/proxmox-asrock
gets in time-out.
# showmount -e 192.168.20.160
Export list for 192.168.20.160:
/home/nfs 192.168.20.160,192.168.20.132,192.168.20.150
This result is correct, but I'm very surprised that it takes more than 1 min. to get it.
From the fedora test client: it is the same: mounting gets in time out.
From the proxmox server itself: the nfs connection on itself works good and immediately => I assume that /etc/export is correct.
Does somebody has got an idea where the issue could come from?
Thanks in advance.
Regards
Arnaud