From owner-freebsd-hackers Tue May 20 10:30:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA14501 for hackers-outgoing; Tue, 20 May 1997 10:30:40 -0700 (PDT) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA14495 for ; Tue, 20 May 1997 10:30:38 -0700 (PDT) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA26502; Tue, 20 May 1997 10:30:18 -0700 Date: Tue, 20 May 1997 10:30:18 -0700 (PDT) From: "Brian N. Handy" To: Doug Rabson Cc: hackers@freebsd.org Subject: Re: Max # of files with NFS? In-Reply-To: Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> So I have this NFS-mounted directory with 287 files in it. If I cd to >> that directory and do an 'ls', that terminal hangs. Top says it's in >> 'getblk'. > > [...] Doug writes: >I just listed a directory with 7800 files it to check. I can't (yet) test >directly with DU 4.0 but if you could get a packet trace, it might help >diagnose what is happening. Run 'tcpdump -vv -s300 port nfs' while you >try to do the 'ls'. Boy, I don't get it...but it works today??? I had to recompile my kernel with the bpf stuff, then I rebooted, mounted the directory, ran tcpdump and did the ls and everything worked fine. I'll keep an eye on this, though, and if I can figure out how to recreate the problem I'll come on back with more info. Thanks, Brian