After Upgrade to 1.6 NFS Issue

M

macday

Member
Mar 10, 2010
408
0
16
Stuttgart / Germany
Hi guys,

last week I update my Proxmox 1.5 Hosts to 1.6. Now I have a big issue.

First my pveversion:

pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.6-19
pve-kernel-2.6.32-4-pve: 2.6.32-19
pve-kernel-2.6.32-1-pve: 2.6.32-4
pve-kernel-2.6.32-2-pve: 2.6.32-8
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-18
pve-firmware: 1.0-8
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-7
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-1
ksm-control-daemon: 1.0-4

If I want to mount an NFS-Share this error comes up:

mount.nfs 10.xx.xx.xx:/mnt/raid5/backup /mnt/pve/nfs
mount.nfs: Cannot allocate memory

Could you help me.

THX
macday


edit: dmesg tells me

lockd_up: makesock failed, error=-12
 
Last edited:
Don't know it is what you are looking for, but I just tried mounting a unfs3 server from within a debian container on a 1.6 (upgraded from 1.5) and it worked without problems.
 
Sorry for my wrong description. I want to mount an nfs-share for vzdumps from the proxmox webinsterface. I got an error. So I tried to mount the nfs-share direct on the host-console and I got the error from post 1. It is just for backups.
 
macday said:
Do I have to downgrade ?
Click to expand...

Well, I can use the same unfs3 server as iso storage from the webinterface as well, so at least it does not seem to be broken for all configurations in 1.6.

Mind, I have been unable to mount nfs servers running the normal user space nfs daemon shipped with debian, unfs3 works fine. I assume this is because nfs protocol 3 is needed, and the "normal" only implements version 2.
 
Well thank you I try that. But I thought unfs3 is only the server. Is there an unfs3 client available?

I have a dedicated NFS-Server based on Ubuntu 10.04 and I want to connect a NFS-Share via the Proxmox Webinterface. This is simply not working after the Upgrade to 1.6

Thanks for help
 
my nfs servers are working, but if you send me you ubuntu nfs setup/config I will try to setup a ubuntu lucid and reproduce the issue in our testlab.
 
/etc/exports from lucid server

/mnt/raid5/backup xx.xx.xx.xx(rw,insecure,async,no_root_squash,no_subtree_check)

perhaps there is something wrong.

thank you
macday
 
using your config file leads to the following error if I restart the nfs-server:


Code: 
/etc/init.d/nfs-kernel-server restart
 * Stopping NFS kernel daemon                                                                                         [ OK ] 
 * Unexporting directories for NFS kernel daemon...                                                                   [ OK ] 
 * Exporting directories for NFS kernel daemon...                                                                            exportfs: /etc/exports:1: syntax error: bad option list
                                                                                                                      [fail]
 
oh yes, was just to blind. fixing this typo leads to a working nfs server. can mount on the web interface.

post your 'pveversion -v'
 
pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.6-19
pve-kernel-2.6.32-4-pve: 2.6.32-19
pve-kernel-2.6.32-1-pve: 2.6.32-4
pve-kernel-2.6.32-2-pve: 2.6.32-8
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-18
pve-firmware: 1.0-8
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-7
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-1
ksm-control-daemon: 1.0-4
 
same version than my test setup with a ubuntu nfs server. works here.
 
Hello,

I did a fresh 1.6 install and I have still the same issue with nfs. For now I´m using sshfs as vzdump-backup-media. I have a Dell PE 840 Server with RAID 10 and bonded network 802.3ad.
 
You must log in or register to reply here.
Top Bottom