Date: Mon, 14 Dec 2009 19:55:13 +0100 From: Jeremie Le Hen <jeremie@le-hen.org> To: John Baldwin <jhb@freebsd.org> Cc: Rick Macklem <rmacklem@freebsd.org>, freebsd-stable@freebsd.org Subject: Re: Cannot list a particular directory through NFS with UDP Message-ID: <20091214185513.GC45540@felucia.tataz.chchile.org> In-Reply-To: <200912141050.40340.jhb@freebsd.org> References: <20091213230650.GA45540@felucia.tataz.chchile.org> <200912141050.40340.jhb@freebsd.org>
index | next in thread | previous in thread | raw e-mail
On Mon, Dec 14, 2009 at 10:50:40AM -0500, John Baldwin wrote:
>
> It looks like the NFS client does not like the replies to the 3819288094
> request. Can you grab nfsstat output before and after a retransmit of
> the request and reply to see which counters are increased? This might
> indicate why the reply is not being accepted.
Premices (replayed each time to have the exact same cache):
# umount /mnt/repos
# mount -t nfs -o intr,soft obiwan:/data/repos /mnt/repos
# cd /mnt/repos/netbsd-cvsroot
# ls
Running ls(1) on a "good" directory shows the following difference:
# ls src
Server: Client:
- +3 getattr - +3 getattr
- +1 lookup - +1 lookup
- +1 readdir - +1 readdir
- +1 access - +1 access
Client cache:
- +9 attrcache
- +2 lookupcache
- +2 readdir
- +2 direofcache
Running ls(1) on the "bad" directory shows the following difference:
# ls pkgsrc
Server: Client:
- +3 getattr - +3 getattr
- +1 lookup - +1 lookup
- +1 readdir - +1 readdir
- +3 access - +3 access
Client cache:
- +5 attrcache
- +1 lookupcache
Both scenarios show no error.
Regards,
--
Jeremie Le Hen
Humans are born free and equal. But some are more equal than others.
Coluche
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091214185513.GC45540>