From owner-freebsd-questions Thu Nov 9 15:51:35 2000 Delivered-To: freebsd-questions@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 999A737B479 for ; Thu, 9 Nov 2000 15:51:33 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eA9NpUE11698; Thu, 9 Nov 2000 15:51:30 -0800 (PST) Date: Thu, 9 Nov 2000 15:51:30 -0800 From: Alfred Perlstein To: Mike Meyer Cc: Christopher Rued , questions@FreeBSD.ORG Subject: Re: crash with fd0/msdos_fs/more Message-ID: <20001109155130.A11449@fw.wintelcom.net> References: <111421183@toto.iv> <14859.14056.493081.289992@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <14859.14056.493081.289992@guru.mired.org>; from mwm@mired.org on Thu, Nov 09, 2000 at 05:44:40PM -0600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Mike Meyer [001109 15:45] wrote: > Christopher Rued types: > > # more I\ Quit.doc > > panic: vm_fault fault on nofault entry addr: c58f200 > > > > << system reboots >> > [...] > > What category would this go into? `misc', `kern', `bin', `i386', > > other? > > Kern. If the machine reboots when it shouldn't, the kernel's at fault. > > Actually, one thing to try before submitting the PR is doing the same > thing as a non-root user, and seeing what happens. I don't completely agree with it, but it's hard for a kernel to cope with a trashed or damaged filesystem: "hrm, this is broke, is because the disk itself is bad or is it because internally I've hosed some of my driver or filesystem data structures... I could continue and disallow writes and possibly reads to/from this bad area... but wait what! if my driver state is hosed... and what if the FS corruption is because I messed up some internal structures... and what is the average air speed velocity of a.." *kernel screams and flys into the chasm* I sort of like how solaris will downgrade a mount to read-only when it detects on disk corruption, this should prevent any further corruption if it's a filesystem of driver bug, but it's not very safe and I'm pretty sure the default is still to panic. Moral of all of this is to use the "mtools" for ms-dog floppy access and "dd+fsck+vnconfig" for UFS floppies. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message