From owner-freebsd-stable Sat Dec 19 19:29:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25857 for freebsd-stable-outgoing; Sat, 19 Dec 1998 19:29:47 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from multivac.fatburen.org (multivac.fatburen.org [62.20.128.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25851 for ; Sat, 19 Dec 1998 19:29:46 -0800 (PST) (envelope-from staffanu@multivac.fatburen.org) Received: (from staffanu@localhost) by multivac.fatburen.org (8.8.8/8.8.8) id EAA10920; Sun, 20 Dec 1998 04:29:34 +0100 (CET) (envelope-from staffanu) To: "Jordan K. Hubbard" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Kernel panic References: <20568.914123603@zippy.cdrom.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Staffan Ulfberg Date: 20 Dec 1998 04:29:32 +0100 In-Reply-To: "Jordan K. Hubbard"'s message of Sat, 19 Dec 1998 19:13:23 -0800 Message-ID: <87zp8jze1v.fsf@multivac.fatburen.org> Lines: 17 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > You fsck'd a live, mounted filesystem? Really?!? I somehow thought that fsck wouldn't even allow modifying a live filesystem, but well, one has to try it to know for sure, right? :) > Of course you paniced. It's not a bug to freak out when a clueless > administrator stomps on the on-disk version of a filesystem and > renders it inconsistent with various cached memory contents. Guilty as charged, I suppose. However, since this was my /var/tmp partition I wasn't too anxious about what would happen. I hadn't expected a panic, though, even if I very well can understand the reasons for it, in retrospect. Staffan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message