From owner-freebsd-current Wed Apr 10 02:48:11 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA17972 for current-outgoing; Wed, 10 Apr 1996 02:48:11 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA17918 for ; Wed, 10 Apr 1996 02:47:34 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id LAA10261; Wed, 10 Apr 1996 11:45:07 +0200 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id LAA00296; Wed, 10 Apr 1996 11:45:06 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id KAA12538; Wed, 10 Apr 1996 10:34:22 +0200 (MET DST) From: J Wunsch Message-Id: <199604100834.KAA12538@uriah.heep.sax.de> Subject: Re: fhtovp: filestart miss To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Wed, 10 Apr 1996 10:34:22 +0200 (MET DST) Cc: kuku@gilberto.physik.rwth-aachen.de In-Reply-To: <199604091551.RAA06812@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at Apr 9, 96 05:51:12 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Christoph P. Kukulies wrote: > > > fhtovp: filestart miss 35001765 vs. 25 > > The NFS file handle code in cd9660 hit again... Perhaps nothing to > > worry much about. It should have sent out a ``stale NFS file handle'' > > Correct - I saw this on the client side (an HP-UX system). That's okay (it's what you're supposed to see after changing the medium on the NFS server), but the log message is just overcautious. The NFS file handle calculation in cd9660 is a bit tricky. Since the authors apparently knew about potential pitfalls in it, it seems that they decided to log the stale file handle conditions on the server, too. So in case the decision to send back the ``stale NFS file handle'' was wrong, one could basically track the reasons. It should perhaps be hidden inside #ifdef DIAGNOSTIC or something else. -- 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. ;-)