Ubuntu
nfs-utils package

  1. Bug #213444
  2. Comment #8

Comment 8 for bug 213444

Revision history for this message
Ulli Horlacher (framstag) wrote : Re: Hardy Heron nfs (client) reports internal error when I attempt to mount with NFS

Update:

I tried mount.nfs from Ubuntu 7.10 (installed in /usr/local/sbin/) :

root@pussy:/# /usr/local/sbin/mount.nfs -V
mount.nfs (linux nfs-utils 1.1.0)

root@pussy:/# /usr/local/sbin/mount.nfs rusnas1a-n1:/vol/rusnas1a_n1_vol3/sw /nfs/rusnas/sw -v -o proto=tcp
mount.nfs: trying 129.69.201.80 prog 100003 vers 3 prot tcp port 2049
mount.nfs: trying 129.69.201.80 prog 100005 vers 3 prot tcp port 4046
rusnas1a-n1:/vol/rusnas1a_n1_vol3/sw on /nfs/rusnas/sw type nfs (proto=tcp)

root@pussy:/# mount | grep /sw
rusnas1a-n1:/vol/rusnas1a_n1_vol3/sw on /nfs/rusnas/sw type nfs (rw,proto=tcp,addr=129.69.201.80)

The mount was successfull!

Again, mount.nfs from Ubuntu 8.04 still fails:

root@pussy:/# umount /nfs/rusnas/sw

root@pussy:/# /sbin/mount.nfs -V
mount.nfs (linux nfs-utils 1.1.2)

root@pussy:/# /sbin/mount.nfs rusnas1a-n1:/vol/rusnas1a_n1_vol3/sw /nfs/rusnas/sw -v -o proto=tcp
mount.nfs: timeout set for Tue May 13 15:19:57 2008
mount.nfs: text-based options: 'proto=tcp,addr=129.69.201.80'
mount.nfs: internal error

Dito with proto=udp