NFS shares Mount

[dnut]

Hello there,
randomly I'm not able to config NFS shares as additional storage in the proxmox I configure

It happens randomly and I don't know why.

I usually proceed as follow:
1. I set up a Freenas VM inside proxmox with physical disk attached driectly to the VM
2. I set up NFS shares inside (virtual) freenas
3. I configure NFS additional storage on proxmox web gui

Everything works like a charm up to here but, sometimes, I don't know why, NFS share doesn't works: "Storage is not online". See attached image. What drives me crazy is that it doesn't happens on every server I setup, just sometimes.

If I df via SSH no NFS share appears to be mounted and I'm not able to make it work

I'm using nfs type 3 on the server side (freenas)

It happened with Proxmox 4.1, and now with 4.2...

Does Somebody found this strange behaviour?

P.s. it happens with a Physical Freenas too

 

[dnut]

In the meanwhile I solved in this way:
1. I modified fstab to instruct operating system to properly mount nfs share
2. I created "directory" storage pointing to the locally mounted nfs share
3. I created a script to manualy mount the shares
4. I inserted into cron something like this "@reboot sleep 300 myscript" to mount nfs share 5 minutes after boot

I needed point #4 cause the nfs are offered by Freenas installed on a VM, so I need to allow the VM to boot before to try to mount nfs share.

P.s. 1 This is a little dangerous cause, if the NFS shares are not available, the automatic backup will end to fill the local file system.
P.s. 2 if I mount nfs share via fstab I need to set freenas to use nfs version 4.

 

[dnut]

Today I had the time to do some testing e to report some data:

Packages version of the server used for testing:

proxmox-ve: 4.2-54 (running kernel: 4.4.10-1-pve)
pve-manager: 4.2-15 (running version: 4.2-15/6669ad2c)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.4.10-1-pve: 4.4.10-54
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-42
qemu-server: 4.0-81
pve-firmware: 1.1-8
libpve-common-perl: 4.0-68
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-55
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-19
pve-container: 1.0-68
pve-firewall: 2.0-29
pve-ha-manager: 1.0-32
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie

I tired to upgrade proxmox to the last package versions of the non-commercial repos to see if that could solve the problem, but with no success.

Tried to mount again NFS3 via web gui and the result is that the storage appears in the webgui but appears as not online.

tried to mount NFS3 via cli and this is the output:

root@pve:~# pvesm add nfs test --path /mnt/pve/test --server 192.168.1.11 --export /mnt/volume/proxmox/test
create storage failed: storage 'test' is not online

tried to mount NFS4 via cli and this is the output:

root@pve:~# pvesm add nfs test --path /mnt/pve/test --server 192.168.1.11 --export /mnt/volume/proxmox/test --options vers=4
create storage failed: storage 'test' is not online

here the output of a pvesm nfsscan 192.168.1.11 (which is a freenas server)

/mnt/volume/proxmox/snapshots-manual 192.168.1.10
/mnt/volume/proxmox/snapshots-daily  192.168.1.10
/mnt/volume/proxmox/test             192.168.1.10
/mnt/volume/proxmox/snapshots-weekly 192.168.1.10

As I already said I'm able to mount the NFS4 share via fstab but not able to mount NFS3 or NFS4 through GUI or trhough pvesm command.

It's funny cause it happens randomly when I configure proxmox servers (6 in the last 2 months, and happened 2 times). The environment and configurations are the very same, but the hardware it's different. All supermicro boards.

Any suggestions?

Thank you

 

[tkienzle]

Hey Everybody!

Same issue here!

root@blade1:~# pvesm add nfs bart2test --path /mnt/pve/bart2test --server 10.0.34.206 --options vers=4 --export /mnt/bart2/nfs/
create storage failed: storage 'bart2test' is not online
root@blade1:~# mount.nfs 10.0.34.206:/mnt/bart2/nfs nfstest/ -vv
mount.nfs: timeout set for Sat Jul 23 20:43:45 2016
mount.nfs: trying text-based options 'vers=4,addr=10.0.34.206,clientaddr=10.0.34.211'
root@blade1:~#

Version:

root@blade1:~# pveversion --verbose
proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve)
pve-manager: 4.2-2 (running version: 4.2-2/725d76f0)
pve-kernel-4.4.6-1-pve: 4.4.6-48
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-39
qemu-server: 4.0-72
pve-firmware: 1.1-8
libpve-common-perl: 4.0-59
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-50
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-14
pve-container: 1.0-62
pve-firewall: 2.0-25
pve-ha-manager: 1.0-28
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie
root@blade1:~#

Freenas:

FreeNAS-9.10-STABLE-201606270534 (dd17351)

Network:

auto eth5.34
iface eth5.34 inet static
        address  10.0.34.211
        netmask  255.255.255.0
    vlan-raw-device eth5

Did you have any success??

Regards from Aachen,

Thomas

 

[brucexx]

Assuming you are dealing with FreeNAS 9.10 - check the DNS and host table on the FreeNAS, I had similar issue but permanently not being able to use the NFS (storage is offline) and it turned out to be a DNS issue (even though DNS 2 and DNS 3 were configured properly).

Check last 2 or 3 posts in this thread:
https://forum.proxmox.com/threads/nfs-shares-storage-is-not-online-500.11121/#post-142982

 

[icalredhat]

check file hosts ( /etc/hosts )on your proxmox and freenas...

 

[VDNKH]

I have the same problem...