mount.nfs4: Cannot allocate memory

Bug #309897 reported by Noel J. Bergman on 2008-12-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nfs-utils (Ubuntu)

Bug Description

While dealing with Bug 305589, Bug 306016 and Bug 308537, I decided to try NFS4. The following is the output:

 # mount -t nfs4 myserver.local:/mnt/EXT1 /tmp/myserver/
 mount.nfs4: Cannot allocate memory

The logs contained:

  Dec 19 22:47:40 jaunty kernel: [ 1500.069764] RPC: failed to contact local rpcbind server (errno 5).
  Dec 19 22:47:40 jaunty kernel: [ 1500.114543] RPC: failed to contact local rpcbind server (errno 5).

so this is likely related to the others, just manifesting as a different error message.

Noel J. Bergman (noeljb) wrote :

It appears that this was caused by not properly having fsid=0 in the NFS4 server config. So pilot error in the config, but a very misleading message from the NFS4 client code.

Steve Langasek (vorlon) on 2009-10-03
Changed in nfs-utils (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers