From owner-freebsd-current Tue Oct 24 13:23:57 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA29894 for current-outgoing; Tue, 24 Oct 1995 13:23:57 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA29885 ; Tue, 24 Oct 1995 13:23:41 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA14040; Tue, 24 Oct 1995 13:15:47 -0700 From: Terry Lambert Message-Id: <199510242015.NAA14040@phaeton.artisoft.com> Subject: Re: ufs_ihashget panic w/ NFS3 To: hsu@freefall.freebsd.org (Jeffrey Hsu) Date: Tue, 24 Oct 1995 13:15:47 -0700 (MST) Cc: terry@lambert.org, current@freefall.freebsd.org In-Reply-To: <199510241952.MAA28720@freefall.freebsd.org> from "Jeffrey Hsu" at Oct 24, 95 12:52:04 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 763 Sender: owner-current@FreeBSD.org Precedence: bulk > What kind of ls? I need to know if you have an aliad for > -F or are using a -l and thus whether you are hitting stat, > lstat, or neither. > > OSF/1 3.4 /bin/usr/ls w/ no options or aliases. > > I have been unable to repeat the problem locally. > > Are you doing it using OSF/1 NFS3? No. I assume it's a V3 problem, then? This is a bit more complicated; probably you'll have to get Doug involved; I have only partial papers and some preliminary stuff that I've had for forever for NFSV3. I *don't* have the state diagrams for everything, and it'd have to be a violation of state on one end or the other. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.