From owner-freebsd-current  Tue Oct 24 12:22:18 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id MAA27311
          for current-outgoing; Tue, 24 Oct 1995 12:22:18 -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 MAA27300
          ; Tue, 24 Oct 1995 12:22:13 -0700
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA13925; Tue, 24 Oct 1995 12:14:20 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199510241914.MAA13925@phaeton.artisoft.com>
Subject: Re: ufs_ihashget panic w/ NFS3
To: hsu@freefall.freebsd.org (Jeffrey Hsu)
Date: Tue, 24 Oct 1995 12:14:20 -0700 (MST)
Cc: current@freefall.freebsd.org
In-Reply-To: <199510240828.BAA27084@freefall.freebsd.org> from "Jeffrey Hsu" at Oct 24, 95 01:28:29 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 770       
Sender: owner-current@FreeBSD.org
Precedence: bulk

> I consistently get an
> 	panic: ufs_ihashget: recursive lock not expected -- pid 95
> when doing an ls in a directory nfs mounted from FreeBSD-current
> (as of this morning) to a DEC OSF/1 machine.  A localhost nfs mount of
> the same directory appears to work fine.

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.

I noticed a potential problem in the code in this area, but thought
it would never get exercised.  Apparently, someone is going bredth
first (unexpected client behaviour).

I have been unable to repeat the problem locally.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.