After restart NFS connection is lost

[BitRausch]

Hi,

after rebooting the pve server NFS is not recognized anymore.
When I go to the web-interface->storage and enable one of the NFS storage mount shows the NFS again.
This happens everytime I reboot the pve server. The NFS Server is always up.

Where should I look to find more information if there is an error during start up?


regards
BitRausch
PS. running the latest PVE version 1.4beta

pve-manager: 1.4-5 (pve-manager/1.4/4330)
qemu-server: 1.1-3
pve-kernel: 2.6.24-14
pve-kvm: 86-4
pve-firmware: 1
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.2-1
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1

 

[tom]

Hi,

after rebooting the pve server NFS is not recognized anymore.
When I go to the web-interface->storage and enable one of the NFS storage mount shows the NFS again.
This happens everytime I reboot the pve server. The NFS Server is always up.

Where should I look to find more information if there is an error during start up?


regards
BitRausch
PS. running the latest PVE version 1.4beta

pve-manager: 1.4-5 (pve-manager/1.4/4330)
qemu-server: 1.1-3
pve-kernel: 2.6.24-14
pve-kvm: 86-4
pve-firmware: 1
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.2-1
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1

this is not unusual, only if a guest or a backup job uses the nfs storage it shows up with mount.

or do you see any problem, does something not work?

 

[BitRausch]

Hi Tom,

Thx for your reply. I am using my pve server mainly for software testing. So I do not start any VM at boot time. But I do have my ISO Images on the NFS Server and I run vzdump manually when I need to backup VM's on my NFS Server.
So if I understand you correctly I need either to start a VM which make use of NFS at boot time ore run a backup job?
Even when the webgui show me that the NFS is enabled and active?

Kind of confusing but not a big probleme since everything else works very well! Would it be better for me to add the NFS Storage to the fstab instead of using the Storage on the WebGUI. Would there be a problem/conflict if I add it to the fstab?

regards
BiRausch

PS. My understanding was that the NFS configuration is more like a permanent entry. Maybe a flag which allows me (and others) to make this permanent can be implemented in the future? just a thought.

 

[tom]

Hi Tom,

Thx for your reply. I am using my pve server mainly for software testing. So I do not start any VM at boot time. But I do have my ISO Images on the NFS Server and I run vzdump manually when I need to backup VM's on my NFS Server.
So if I understand you correctly I need either to start a VM which make use of NFS at boot time ore run a backup job?
Even when the webgui show me that the NFS is enabled and active?

Kind of confusing but not a big probleme since everything else works very well! Would it be better for me to add the NFS Storage to the fstab instead of using the Storage on the WebGUI. Would there be a problem/conflict if I add it to the fstab?

regards
BiRausch

PS. My understanding was that the NFS configuration is more like a permanent entry. Maybe a flag which allows me (and others) to make this permanent can be implemented in the future? just a thought.

I still not get it. If you have a VM using ISO on NFS it should just work, otherwise its a bug.

vzdump: the very latest version (will be released soon) has a dropdown to select the storage.

to understand:
so you defined the storage for backups (NFS), then you reboot and then you want to start vzdump on the console using the NFS backup storage?

I will test this.

 

[BitRausch]

Hi tom,

maybe I was not clear.

I still not get it. If you have a VM using ISO on NFS it should just work, otherwise its a bug.

Thats what is happening - I think.
This is what I do:

I have 2 NFS storage defined through the GUI - one for my backups and one for ISO's (both are active+enabled+shared). After a reboot when I try to access the directory /mnt/pve/proxmoxiso for example (console) it will not show me anything. Mount does not show the NFS connection. Then when I go to the Web-GUI->Storage and enable one of the NFS entries (just hit the red arrow and click enable even so everything is active and enabled) then go back to the console and execute mount both NFS connection show up and I can access the ISO's again. This is what I have to do every time I reboot.

Hope this explains it better?

kind regards

PS. The main reason why I do this is to copy files between the NFS storage and the pve server with mc.

 

[dietmar]

. After a reboot when I try to access the directory /mnt/pve/proxmoxiso for example (console) it will not show me anything.

Yes, that is the intended behaviour - why is this a problem? New vzdump has a --storage options (instead of --dumpdir), which automatically activates the storage.

 

[BitRausch]

Hi Dietmar,

Thank you for your reply.
Ok. Now I understand. I thought once you have setup a storage it will be always setup automatically during boot sequence. Kind of like entering the NFS directory in the fstab.


What I am looking for is to have the NFS storage connected during boot sequence so I do not have to do it every time.


Question:

Can I add the NFS storage connection in fstab and have it setup in the Web-GUI at the same time without any problems?


regards
BitRausch
PS. It is not a problem. Just a matter of understanding how to use it correctly.

 

[dietmar]

Can I add the NFS storage connection in fstab and have it setup in the Web-GUI at the same time without any problems?

Yes, but use the 'directory' storage type on the Web-GUI instead (no need to configure the nfs server twice).

 

[BitRausch]

understood. Thank you dietmar.