From owner-freebsd-bugs Mon Apr 21 21:50:45 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA13367 for bugs-outgoing; Mon, 21 Apr 1997 21:50:45 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA13362 for ; Mon, 21 Apr 1997 21:50:42 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA23489; Tue, 22 Apr 1997 00:50:09 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 22 Apr 1997 00:50 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id WAA08671; Mon, 21 Apr 1997 22:44:55 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id WAA02885; Mon, 21 Apr 1997 22:51:23 -0400 (EDT) Date: Mon, 21 Apr 1997 22:51:23 -0400 (EDT) From: Thomas David Rivers Message-Id: <199704220251.WAA02885@lakes.water.net> To: ponds!nlsystems.com!dfr, ponds!lakes.water.net!rivers Subject: Re: kern/3304: NFS V2 readdir hangs Cc: ponds!freefall.cdrom.com!freebsd-bugs Content-Type: text Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > udp: > > 5 dropped due to full socket buffers > >... > > > > ip: > > 5 packets reassembled ok > >... > > > > Yes! - this particular change does work-around the problem. I'm > > able to run my "ls -lR" and have it complete successfully [although, > > there are some strange 'lags' every now and then...] it does work. > > I've been running it continuously for a few minutes now; no hangs... > > Well that is a start. I need to fix up mount_nfs so that you can frob > with the directory read size in these cases. > > > > > Now - a good question, which you asked, is why are those packets > > getting blocked? > > > > Also, another question I have is why did this work with 2.1.5 - did > > it always have a lower readdirsize; or is another problem in 2.2.1 simply > > masked by lowering the readdirsize? > > The readdir code at this level was quite a bit different. I don't know > whether it would have read smaller blocks but it would have certainly read > different ones at different offsets. > > > > > I'm happy to investigate this further - and *overjoyed* that NFS > > seems to be working for me... let me know what I can do at this end. > > I think the most promising candidate is the 'full socket buffers' message. > Could you see if that goes up consistently when you prompt the system to > hang. The match between that and the reassembly number seems to show that > these are large packets. We'll do! > > I am going to bed now. Good luck in your detective work! Thanks again for your help! - Dave Rivers - > > -- > Doug Rabson Mail: dfr@nlsystems.com