New Member

Well this is very odd. As a workaround overnight I removed the Backups storage and created a new NFS mount on each node at /mnt/pve/Backup2 and created a new Storage Dir using the UI called Backup2. I changed my backup jobs to back up to Backup2 and tested them, everything was working fine.

Today I read your message and sat down to do some troubleshooting. Once again I added a new NFS storage called Backups and was ready to comb through the syslog when suddenly everything works.

I made no other changes to the system and I did not reboot. Is it possible that changing the location which the backup jobs point to resolved the issue?

In any case, everything is fine now. Thank you for your time and your suggestions, I didn't think to look in syslog.

New Member

I also get this error on my cluster after upgrading it from Proxmox 1.x to 2.0
The only workaround to re-enable the NFS shares (at least for some days) is to restart the nfs server on my NAS (Synology).

How ever, after the time the error comes back, the nfs shares seams to be offline again and I have to restart the nfs server once more.

New Member

New Member

Sorry to excave an old post, but with fresh install of proxmox 3.1 I can reproduce this problem everytime between some Dell workstations, and a QNAP TS-469L NAS or any other linux servers/VM on the local network.

I tested a dell optiplex 745 with broadcom network chipset, and a dell T3600 with a TG3 network chipset.

So proxmox complains about storage being offline, I won't blame the proxmox storage daemon on this : rpcinfo -p should not timeout.

The problem is that :
- Other linux boxes on the network do not suffer from this problem.
- The proxmox server v3.0 upgraded to v3.1 do not suffer from this problem.
- Without -p option, "rpcinfo 172.16.66.66" finally works after a very long time.
- When running "rpcinfo -p serverip" Wireshark show a SYN but no ACK in reply (hence the timeout)
- When running "telnet serverip 111" Wireshark show a SYN and ACK in reply (explain me this)

On top of that, this mount command line works :

Code:

# mount -t nfs -o vers=3,udp serverip:/Backup /mnt/pve/Backup

But this mount command doesn't works :

Code:

# mount -t nfs -o vers=3 serverip:/Backup /mnt/pve/Backup

This problem feels very wrong and bizarre. The switch is an HP 2530-24G, and there is no trace of firewall installed.

Since the problem arises with any other server (not only the NAS), I guess the NAS is not to blame, and rebooting the NAS has no effect on this, I tried removing the IPV6 (following a tutorial on internet) with no success.

Does somebody have any clue about this problem ? It drives me nuts.
How did you managed to disable the NFSv4 and IPV6 on the proxmox host ?

New Member

Onliest to register. Recently i had problem with the access on my nfs storage.
I'm using Proxmox 4.2
The message that i receive was "NFS_Storage is not online"

I read on https://forums.freenas.org/index.php?threads/nfs-mount-times-out.7270/ :
"During the mount process, NFS apparently does a reverse DNS lookup to see if the address is valid. On a local network there is no way to do that unless you add the IP address of the client to the hosts file on the server. The hosts file even mentions that in the documentation in the beginning of the file. Once we did that the mount connected very quickly."

So I register my servers on /etc/hosts of FreeNAS. And the message changed to "NFS version ..."
Then I changed on FreeNAS to permit use NFS v4.

But when the FreeNAS reboot the /etc/hosts is rewrited, so to make the register of hosts permanent need to register the hosts on FreeNAS.
"System > Network", on field "Host name data base"

Member

Thanks Bruno - your post lead me to the issue I was having. I was getting the same Storage is not online message. I checked everything on Proxmox side and it was ok. When I saw your post I went to the network setting on the FreeNAS and noticed that the DNS 1 was not valid anymore (I replaced it a week ago and the ip address changed), the DNS2 and 3 had a valid public DNS ips 8.8.8.8 and 4.2.2.2 but I guess it was not enough, go figure...

Once I adjusted the primary DNS setting even with no host name database entry for Proxmox it started to work immediately.

New Member

pretty old thread but I did experiment the same issue today,
i was able to connect in the shell with a classic mount, but got always an error on the Proxmox side,

I got it finally working by editing /etc/pve/storage.cfg
i noticed that proxmox was using nfs version 3, but my nfs server at ovh wanted nfs 4
so by just changing the line
options vers=3
to
options vers=4

Problem
I was switching the backing store of several VMs from iSCSI to NFS (QCoW2) storage when I encountered the error TASK ERROR: storage 'nfs-infra-ssd-1' is not online. In one of the PVE nodes, the NFS storage showed up as inactive.

Code:

# pvesm status
...
nfs-infra-ssd-1 nfs inactive 0 0 0 0.00%

Solution
I didn't manage to figure out what was the issue but remounting the share made it active again.

Quick Navigation

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.