From owner-freebsd-hackers Fri Nov 8 14:23:23 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA14018 for hackers-outgoing; Fri, 8 Nov 1996 14:23:23 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA13983 for ; Fri, 8 Nov 1996 14:23:09 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA27117; Fri, 8 Nov 1996 23:21:46 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA16376; Fri, 8 Nov 1996 23:21:42 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.2/8.6.9) id XAA07826; Fri, 8 Nov 1996 23:14:16 +0100 (MET) From: J Wunsch Message-Id: <199611082214.XAA07826@uriah.heep.sax.de> Subject: Re: Strange messages from my 2.1.0 kernel To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Fri, 8 Nov 1996 23:14:16 +0100 (MET) Cc: john@starfire.mn.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199611081855.MAA04307@starfire.mn.org> from "john@starfire.mn.org" at "Nov 8, 96 12:55:02 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As john@starfire.mn.org wrote: > > > fhtovp: file start miss 1946157056 vs 68 > > > > It might mean you have two nfsnodes pointing to the same vnode... > > Or it might mean someone is trying to NFS hack your system... > > Or it might be an mmap() of an NFS file on an FS with a 4k block > > size and an NFS rzise/wsize of 8K, or vice versa... Or it might be that Terry forgot to use grep(1), so he didn't notice that these messages are from cd9660 f/s... Actually, the cd9660 code is by far too blatant in spitting out kernel printf's whenever it is going to reject a request with a ``stale file handle'' response. > Oh! OK! That makes perfect sense, then. A remote system had had > my CD NFS mounted, but I rebooted, and my CD does not get automatically > booted on mount (I hate to automatically mount removeable media). Why do you hate this? Because someone (IMHO stupidly) made a failure mounting a CD-ROM a fatal error? This can easily be avoided (and i do avoid it). I always disliked this idea. Simply reorganize your /etc/rc so that only mount failures for filesystems that are essential for you will abort the script. Take away the `noauto' for the CD-ROM, and simply try mounting it at boot time. If it's not there, /etc/rc will go on without complaints (except from mountd later about not being able to change the NFS export attributes for /cdrom, but that's benign). -- 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. ;-)