NFS problem with past 2.6.31 git tree

From: Zdenek Kabelac
Date: Fri Sep 25 2009 - 11:12:32 EST


Hi

I've noticed that my qemu guest is now unable to use localy exported
nfs directory.
Directory gets mounted, plain 'ls' shows filenames - but nothing else
could be done.

ls -la gives this output:
ls: cannot access patch: Input/output error
...


Both host & guest are running same kernel:
851b147e4411df6a1e7e90e2a609773c277eefd2

I've checked last few commits and tried to revert them -
and this one seems to cure my problem when reverted:

Sep 23: 8a6e5deb8a8caa810fef2c525f5dbea2cfe04a47
NFS: Get rid of the NFS_MOUNT_VER3 and NFS_MOUNT_TCP flags

I should also probably note that I'm seeing this message in my dmesg log:
svc: failed to register lockdv1 RPC service (errno 97)

rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 53550 status
100024 1 tcp 44174 status
100021 1 udp 49878 nlockmgr
100021 3 udp 49878 nlockmgr
100021 4 udp 49878 nlockmgr
100021 1 tcp 47319 nlockmgr
100021 3 tcp 47319 nlockmgr
100021 4 tcp 47319 nlockmgr

automount(pid1720) /misc autofs
rw,relatime,fd=4,pgrp=1720,timeout=300,minproto=2,maxproto=4,indirect
0 0
192.168.122.1:/home/u/export /misc/u nfs
rw,relatime,vers=3,rsize=524288,wsize=524288,namlen=255,soft,proto=tcp,port=65535,timeo=600,retrans=2,sec=sys,mountaddr=192.168.xxx.yyy,mountvers=3,mountproto=tcp,addr=192.168.xxx.yyy
0 0


Zdenek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/