From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Trond.Myklebust@netapp.com
Subject: NFS problem with past 2.6.31 git tree
Date: Fri, 25 Sep 2009 17:12:24 +0200 [thread overview]
Message-ID: <c4e36d110909250812g74e049b7u39566d189970d77e@mail.gmail.com> (raw)
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
next reply other threads:[~2009-09-25 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 15:12 Zdenek Kabelac [this message]
2009-09-25 15:27 ` Trond Myklebust
2009-09-25 19:46 ` Zdenek Kabelac
2009-09-25 23:08 ` Trond Myklebust
2009-09-28 17:50 ` Trond Myklebust
2009-09-30 6:55 ` Zdenek Kabelac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4e36d110909250812g74e049b7u39566d189970d77e@mail.gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®