On Mar 1, 2013, at 6:43 AM, Jan Engelhardt <jengelh@xxxxxxx> wrote:
> Hi.
>
>
> I had here a case with a Linux 3.7.9 system, a virtual machine in a
> RFC1918 range, that did not want to mount NFS.
>
> linux-3lzm:~ # strace -fe mount mount -t nfs 134.76.12.5:/X /mnt
> Process 1477 attached
> [pid 1515] mount("134.76.12.5:/X", "/mnt", "nfs", 0, "vers=4,addr=134.76.12.5,clientaddr=0.0.0.0") = -1 EIO (Input/output error)
"clientaddr=0.0.0.0" is interesting: perhaps the mount.nfs command should have failed right there.
But, let's find out why the kernel is returning EIO. Enter:
# rpcdebug -m nfs -s all
# rpcdebug -m rpc -s call xprt
Try your NFSv4 mount command again, then post relevant excerpts from the kernel log.
By the way, does this happen on older kernels?
> mount.nfs: mount system call failed
> [pid 1477] +++ exited with 32 +++
> --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=1477, si_status=32, si_utime=0, si_stime=0} ---
> +++ exited with 32 +++
>
> Nothing in dmesg...
>
> [ 84.202243] RPC: Registered named UNIX socket transport module.
> [ 84.202246] RPC: Registered udp transport module.
> [ 84.202248] RPC: Registered tcp transport module.
> [ 84.202249] RPC: Registered tcp NFSv4.1 backchannel transport module.
> [ 84.205909] FS-Cache: Loaded
> [ 84.208782] FS-Cache: Netfs 'nfs' registered for caching
> [ 84.215733] NFS: Registering the id_resolver key type
> [ 84.215762] Key type id_resolver registered
> [ 84.215763] Key type id_legacy registered
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
