Date: Wed, 10 Apr 1996 10:34:22 +0200 (MET DST) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-current@FreeBSD.org (FreeBSD-current users) Cc: kuku@gilberto.physik.rwth-aachen.de Subject: Re: fhtovp: filestart miss Message-ID: <199604100834.KAA12538@uriah.heep.sax.de> In-Reply-To: <199604091551.RAA06812@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at Apr 9, 96 05:51:12 pm
next in thread | previous in thread | raw e-mail | index | archive | help
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. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199604100834.KAA12538>