Re: Cannot list a particular directory through NFS with UDP

2010-01-02 Thread Jeremie Le Hen
Rick, Thanks for your time on this. On Thu, Dec 31, 2009 at 02:23:32PM -0500, Rick Macklem wrote: [stuff snipped] This appears to be the reply to the nfs readdir request, which is what would be expected. It could be a problem with the content or the reply or a NetBSD client issue. If

Re: Cannot list a particular directory through NFS with UDP

2010-01-02 Thread Rick Macklem
On Sat, 2 Jan 2010, Jeremie Le Hen wrote: I will reduce the MTU and see if the problem arises with directories that could be read correctly otherwise. I will keep you informed. You can reduce rsize to 1024, so that it isn't happening, but that will also change the size of the readdir

Re: Cannot list a particular directory through NFS with UDP

2009-12-31 Thread Rick Macklem
On Tue, 29 Dec 2009, Jeremie Le Hen wrote: [stuff snipped] This appears to be the reply to the nfs readdir request, which is what would be expected. It could be a problem with the content or the reply or a NetBSD client issue. If you were to email me the raw tcpdump capture for the above, I

Re: Cannot list a particular directory through NFS with UDP

2009-12-31 Thread Jeremy Chadwick
On Thu, Dec 31, 2009 at 02:23:32PM -0500, Rick Macklem wrote: On Tue, 29 Dec 2009, Jeremie Le Hen wrote: [stuff snipped] This appears to be the reply to the nfs readdir request, which is what would be expected. It could be a problem with the content or the reply or a NetBSD client issue.

Re: Cannot list a particular directory through NFS with UDP

2009-12-29 Thread Jeremie Le Hen
Hi Rick, Sorry for the delayed reply, but I have had little time available with Christmas. On Fri, Dec 18, 2009 at 03:23:44PM -0500, Rick Macklem wrote: 00:00:01.953196 IP (tos 0x0, ttl 64, id 48966, offset 0, flags [none], proto UDP (17), length 168) 192.168.1.1.3819288094

Re: Cannot list a particular directory through NFS with UDP

2009-12-18 Thread Rick Macklem
On Mon, 14 Dec 2009, Jeremie Le Hen wrote: 00:00:01.953196 IP (tos 0x0, ttl 64, id 48966, offset 0, flags [none], proto UDP (17), length 168) 192.168.1.1.3819288094 192.168.1.222.2049: 140 readdir [|nfs] 00:00:01.953665 IP (tos 0x0, ttl 64, id 27028, offset 0, flags [+], proto UDP (17),

Re: Cannot list a particular directory through NFS with UDP

2009-12-14 Thread Rick Macklem
On Mon, 14 Dec 2009, Jeremie Le Hen wrote: Hi, __ Please Cc: me when replying as I'm not subscribed. Thanks. __ My NFS server is running FreeBSD 8.0 from December 6th. The client is a NetBSD 5.0. The directory exported is /data/repos on the server (192.168.1.222) and is mounted on

Re: Cannot list a particular directory through NFS with UDP

2009-12-14 Thread John Baldwin
On Sunday 13 December 2009 6:06:50 pm Jeremie Le Hen wrote: Hi, __ Please Cc: me when replying as I'm not subscribed. Thanks. __ My NFS server is running FreeBSD 8.0 from December 6th. The client is a NetBSD 5.0. The directory exported is /data/repos on the server (192.168.1.222) and

Re: Cannot list a particular directory through NFS with UDP

2009-12-14 Thread Jeremie Le Hen
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

Re: Cannot list a particular directory through NFS with UDP

2009-12-14 Thread Jeremie Le Hen
Hi Rick, On Mon, Dec 14, 2009 at 11:14:06AM -0500, Rick Macklem wrote: My NFS server is running FreeBSD 8.0 from December 6th. The client is a NetBSD 5.0. The directory exported is /data/repos on the server (192.168.1.222) and is mounted on /mnt/repos on the client (192.168.1.1). The

Cannot list a particular directory through NFS with UDP

2009-12-13 Thread Jeremie Le Hen
Hi, __ Please Cc: me when replying as I'm not subscribed. Thanks. __ My NFS server is running FreeBSD 8.0 from December 6th. The client is a NetBSD 5.0. The directory exported is /data/repos on the server (192.168.1.222) and is mounted on /mnt/repos on the client (192.168.1.1). The problem