NFS stopped working

G

gkovacs

Renowned Member
Dec 22, 2008
516
51
93
Budapest, Hungary
I have an NFS share on a separate physical Windows Server 2003 machine which I use for daily network backups of my VE's. Yesterday I've applied fixes to both the Win (via Windows Update) and the Proxmox machines (apt-get dist-upgrade, also changed the IO scheduler to 'deadline'), and now NFS doesn't work anymore.

Previously under 'Storage list' the NFS share was shown with free space of the drive correctly stated. Now all it says is 0.
If I click on it to browse, the following error comes up:
Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, root and inform them of the time the error occurred, and anything you might have done that may have caused the error.

[8151]ERR: 24: Error in Perl code: command '/bin/mount -t nfs 10.0.0.1:/NFS /mnt/pve/nfsbackup' failed with exit code 32

Apache Embperl 2.2.0 [Mon Jun 14 03:54:56 2010]
Click to expand...

Scanning the NFS server's IP on the 'Add NFS Share' page gives the following error:
Error: command '/sbin/showmount --no-headers --exports 10.0.0.1' failed with exit code 1
Click to expand...
While I understand it might not be a Proxmox problem, I would still very much welcome any help into how to diagnose this.
 
Last edited:
Entering the same mount command in the shell produces the following output:

proxmox:~# /bin/mount -t nfs 10.0.0.1:/NFS /mnt/pve/nfsbackup
mount.nfs: mount to NFS server '10.0.0.1' failed: RPC Error: Program not registered
Click to expand...

Does this mean it's a problem on the Windows side, where the NFS share resides?
 
You must log in or register to reply here.
Top Bottom