Package: nfs-utils
Version: 1:1.1.2-2
Severity: important

Coin,

I just discovered i could not mount my NFS4 shares again (did not try any NFS3 shares, so i don't know if it is NFS4-specific or not) ; the mount command hanged a moment and then failed with the following message:
  mount.nfs4: internal error
In the dmesg i could find:
  May  1 11:06:37 Vingilot kernel: nfs: server elwin not responding, timed out
May 1 11:06:46 Vingilot kernel: rpcbind: server elwin not responding, timed out Which is strange because the last character of the hostname is removed (the hostname is "elwing"). I then tried with the FQDN "elwing.hq.duckcorp.org", and got the same result with the "g" of "org" removed.

Adding an extra letter at the end of the hstname resulted in:
  mount.nfs4: can't get address for elwingz
so i guess this may just be a cosmetic bug.

I also tried to deactivate IPv6, even if it never interfered in the past, but got the same result.

Both hosts were using the same exact nfs-utils version, so i checked the kernel version and both are using linux-image-2.6.24-1-xxx 2.6.24-6, one on i386, the other on amd64. I tried the easiest, to downgrade nfs-utils to 1:1.1.1-14, and everything started to work like a charm again.

--
Marc Dequènes (Duck)

Attachment: pgpMu3SCbZmnO.pgp
Description: PGP Digital Signature

Reply via email to