From owner-freebsd-hackers  Sat Jan 13 16:05:18 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA27424
          for hackers-outgoing; Sat, 13 Jan 1996 16:05:18 -0800 (PST)
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA27407
          for freebsd-hackers@freebsd.org; Sat, 13 Jan 1996 16:04:56 -0800 (PST)
From: j@uriah.heep.sax.de
Message-Id: <199601140004.QAA27407@freefall.freebsd.org>
Date: Fri, 12 Jan 1996 22:05:38 +0100 (MET)
Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
In-Reply-To: <199601120907.KAA09020@gilberto.physik.rwth-aachen.de> from "Christoph Kukulies" at Jan 12, 96 10:07:10 am
X-Phone: +49-351-2012 669
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
To: undisclosed-recipients:;
Sender: owner-hackers@FreeBSD.ORG
Precedence: bulk

As Christoph Kukulies wrote:
> 
> After booting the server I noticed the stale handle. So I looked in
> the server and found that the file system of the disk in question
> was so screwed (BAD DATA IN SUPERBLOCK or something) that even
> a fsck -b 32 -y did not recover the filesystem on the ultrix side.
> So I decided to newfs and mount the disk again.

Then it's normal that you've got a stale NFS file handle.  The server
is computing the NFS file handle it hands off to the clients based on
the layout of the file system.  It's guaranteed that you will get the
same file handle again as long as the file system layout is identical,
but after revamping the file system from ground of, all file handles
will become stale.  That's rather intention, not a bug.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)