NFS error (exit code 32)

Discussion in 'Proxmox VE 1.x: Installation and configuration' started by ltor, Nov 10, 2010.

  1. ltor

    ltor Member

    Joined:
    Jun 1, 2010
    Messages:
    35
    Likes Received:
    0
    Hello,
    I read some posts about nfs errors here but without finding a solution...
    We have a cluster (two nodes) of Proxmox 1.6 updated.
    An other server (Centos updated) exports a LVM volume (ext3) of 4.8 TB with rw and no_root_squash options.
    The exportfs command is OK
    The Iptables are Off
    The partition to export is 777
    We are on the same Vlan
    From CTO, I can do telnet 111 and telnet 2049 towards the NFS server.

    But when I do "add a volume storage" and indicate the NFS server, the good point is that "Scan" button detect the partition to mount, the bad point is that when I try to "Activate" I get a "failed with exit code 32"

    In the log, we have numerous "nfs : Unknown Symbol" (cf. infra)

    Anyone an idea ?

    Thanks in adance

    LT

    Nov 10 11:11:52 kernel nfs: Unknown symbol nfs_debugNov 10 11:11:52 kernel nfs: Unknown symbol sunrpc_cache_updateNov 10 11:11:52 kernel nfs: disagrees about version of symbol set_anon_superNov 10 11:11:52 kernel nfs: Unknown symbol set_anon_superNov 10 11:11:52 kernel nfs: Unknown symbol rpc_destroy_wait_queueNov 10 11:11:52 kernel nfs: Unknown symbol xdr
     
  2. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    16,216
    Likes Received:
    270
    What is the output of:

    # pveversion -v
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. ltor

    ltor Member

    Joined:
    Jun 1, 2010
    Messages:
    35
    Likes Received:
    0
    Thanks for you interest,
    Here is the command result :

    # pveversion -v
    pve-manager: 1.6-5 (pve-manager/1.6/5261)
    running kernel: 2.6.32-4-pve
    proxmox-ve-2.6.32: 1.6-25
    pve-kernel-2.6.32-4-pve: 2.6.32-25
    pve-kernel-2.6.18-2-pve: 2.6.18-5
    qemu-server: 1.1-22
    pve-firmware: 1.0-9
    libpve-storage-perl: 1.0-14
    vncterm: 0.9-2
    vzctl: 3.0.24-1pve4
    vzdump: 1.2-8
    vzprocps: 2.0.11-1dso2
    vzquota: 3.0.11-1
    pve-qemu-kvm: 0.12.5-2
    ksm-control-daemon: 1.0-4
     
  4. ltor

    ltor Member

    Joined:
    Jun 1, 2010
    Messages:
    35
    Likes Received:
    0
    I tried to mount "manually" on CT0 the exported partition :

    CT0:~# mount x.x.x.x:/sauvegarde /toto
    mount.nfs: No such device

    It seems like if NFS was disabled in the kernel (?)...
     
  5. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    16,216
    Likes Received:
    270
    You already loaded the module?

    # modprobe nfs
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. ltor

    ltor Member

    Joined:
    Jun 1, 2010
    Messages:
    35
    Likes Received:
    0
    Yes, I tried "modprobe nfs" and the result was error messages and a suggestion to see "dmesg" log where I found numerous "nfs : unknown symbol" as in the Proxmox log.
    Am I the only one with this kind of problem or are the error messages leading us to a bad interpretation of the problem ?
    Thanks for your help
     
  7. tom

    tom Proxmox Staff Member
    Staff Member

    Joined:
    Aug 29, 2006
    Messages:
    13,033
    Likes Received:
    333
    modprobe nfs should not produce any error.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. ltor

    ltor Member

    Joined:
    Jun 1, 2010
    Messages:
    35
    Likes Received:
    0
    I agree with you but what to do ?
    Is this a kernel bug ?
    Is there a "very stable" release to try ?

    Thanks
     
  9. stef1777

    stef1777 Member

    Joined:
    Jan 31, 2010
    Messages:
    176
    Likes Received:
    8
    Use Kernel 2.6.18 in place of 2.6.32 and NFS will work fine with Proxmox 1.6.
     
  10. ltor

    ltor Member

    Joined:
    Jun 1, 2010
    Messages:
    35
    Likes Received:
    0
    Thank you very much, that was the problem !

    I am quite surprised as my collegues that new kernel does not support NFS...Why ?
     
  11. stef1777

    stef1777 Member

    Joined:
    Jan 31, 2010
    Messages:
    176
    Likes Received:
    8
    NFS should be supported with 2.6.32 but is curently buggy.

    Have you tried with Kernel 2.6.24?
     
  12. ltor

    ltor Member

    Joined:
    Jun 1, 2010
    Messages:
    35
    Likes Received:
    0
    Now, we stay in the only stable version mentionned on the Proxmox web site.
    Thanks again for the tip.
    What we found curious was to propose unstable version as update or default kernel during a new installation...
     
  13. stef1777

    stef1777 Member

    Joined:
    Jan 31, 2010
    Messages:
    176
    Likes Received:
    8
    The problem is that 2.6.18 is not very nice to use with last hardware as HP G6/G7 ou Dell Rxxx. Lack of support for these new hardwares.

    I will be interested too to have a system to select the right kernel at proxmox install.
     
  14. ltor

    ltor Member

    Joined:
    Jun 1, 2010
    Messages:
    35
    Likes Received:
    0
    I understand now and that's right that a kernel choice during the setup will be great !

    I must create new Hard Nodes on Dell R710 so I may be disappointed if HardWare support and NFS cannot co-exist...I will see...

    Best regards
     
  15. stef1777

    stef1777 Member

    Joined:
    Jan 31, 2010
    Messages:
    176
    Likes Received:
    8
    More on NFS and Promox 1.6 (with Kernel 2.6.18).

    NFS mount doesn't work with the Debian x64 OpenVZ template. Works fine with i386 template.

    We got "no such device".
     
  16. JMoreno

    JMoreno Member

    Joined:
    Oct 26, 2011
    Messages:
    51
    Likes Received:
    0
    Hi,

    I have same problem here in two different ProxMox servers:

    PM1 =

    pve-manager: 1.9-24 (pve-manager/1.9/6542)
    running kernel: 2.6.32-6-pve
    proxmox-ve-2.6.32: 1.9-47
    pve-kernel-2.6.32-6-pve: 2.6.32-47
    qemu-server: 1.1-32
    pve-firmware: 1.0-14
    libpve-storage-perl: 1.0-19
    vncterm: 0.9-2
    vzctl: 3.0.29-2pve1
    vzdump: 1.2-16
    vzprocps: 2.0.11-2
    vzquota: 3.0.11-1
    pve-qemu-kvm: 0.15.0-1
    ksm-control-daemon: 1.0-6


    PM2 =

    pve-manager: 1.9-24 (pve-manager/1.9/6542)
    running kernel: 2.6.18-6-pve
    proxmox-ve-2.6.18: 1.8-15
    pve-kernel-2.6.18-2-pve: 2.6.18-5
    pve-kernel-2.6.18-6-pve: 2.6.18-15
    qemu-server: 1.1-32
    pve-firmware: 1.0-14
    libpve-storage-perl: 1.0-19
    vncterm: 0.9-2
    vzctl: 3.0.29-2pve1
    vzdump: 1.2-16
    vzprocps: 2.0.11-2
    vzquota: 3.0.11-1
    pve-qemu-kvm-2.6.18: 0.9.1-15

    Any idea?

    Thanks.
     
  17. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    16,216
    Likes Received:
    270
    What exactly is 'the same' problem?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. JMoreno

    JMoreno Member

    Joined:
    Oct 26, 2011
    Messages:
    51
    Likes Received:
    0
    Hi,

    Thanks for your reply.

    I get the following error message:

    Error: command '/bin/mount -t nfs 172.16.2.85:/nethdd/ProxMox /mnt/pve/BackUpExterno' failed with exit code 32.

    In both ProxMox servers, I must say.
     
  19. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    16,216
    Likes Received:
    270
    What output do you get if you run that command manually (ssh login):

    # mount -t nfs 172.16.2.85:/nethdd/ProxMox /mnt/pve/BackUpExterno
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  20. JMoreno

    JMoreno Member

    Joined:
    Oct 26, 2011
    Messages:
    51
    Likes Received:
    0
    Hi again,

    After runnig:

    proxmox3:~/backup# mount -t nfs 172.16.2.85:/nethdd/ProxMox /mnt/pve/BackUpExterno
    mount.nfs: mount to NFS server '172.16.2.85' failed: RPC Error: Program not registered

    Thanks.
     
    #20 JMoreno, Oct 26, 2011
    Last edited: Oct 26, 2011
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice