Comment 6 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

I run into the same problem:

pussy (the client) is an AMD 64X2 PC with 64 bit Ubuntu 8.04.

rusnas1a-n1 is a Netapp FAS 3070 running ONTAP 7.2.1 (a multi-million-Dollar
NAS/SAN):

root@pussy:/# mount.nfs rusnas1a-n1:/vol/rusnas1a_n1_vol3/sw /nfs/rusnas/sw
mount.nfs: internal error

root@pussy:/# strace mount.nfs rusnas1a-n1:/vol/rusnas1a_n1_vol3/sw /nfs/rusnas/sw
(...)
mount("rusnas1a-n1:/vol/rusnas1a_n1_vol3/sw", "/nfs/rusnas/sw", "nfs", 0, "addr=129.69.201.80") = -1 EIO (Input/output error)
write(2, "mount.nfs: internal error\n", 26mount.nfs: internal error) = 26
exit_group(32) = ?

The same client (hardware) with Ubuntu 7.10 can NFS-mount the Netapp
server without any problems.

Mounting an Ubuntu-PC works ok, too.
fex is an Intel Xeon based VMware virtual PC running Ubuntu 7.10:

root@pussy:/# mount.nfs fex:/export/sw /nfs/fex/sw
root@pussy:/# df /nfs/fex/sw
Filesystem 1K-blocks Used Available Use% Mounted on
fex:/export/sw 82567232 24686464 53686592 32% /nfs/fex/sw
root@pussy:/# mount | grep fex
fex:/export/sw on /nfs/fex/sw type nfs (rw,addr=129.69.1.11)

Only the Netapp NFS-Server is not mountable from Ubuntu 8.04. But this is
our central storage device!
"internal error" does not help much in finding the reason of the problem.