From owner-freebsd-current Tue Sep 22 21:08:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22897 for freebsd-current-outgoing; Tue, 22 Sep 1998 21:08:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22808 for ; Tue, 22 Sep 1998 21:07:28 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with SMTP id AAA08027; Wed, 23 Sep 1998 00:08:44 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Wed, 23 Sep 1998 00:08:44 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: ben@rosengart.com cc: current@FreeBSD.ORG Subject: Re: further debugging woes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The automatic fsck failed with an unexpected softupdates inconsistency. > I ran fsck manually, and then, as an experiment, ran it again. The > second time, it found a link count of -11 that should have been 2 that > it missed during the first manual run! > > Just for kicks: soft updates, latest source, BT-948, two SCSI disks, one > processor, a.out, no special patches running. blah :P lucky man, i just had to totally restore a system because 3.0 thought /usr looked like a more comfy spot than my swap for a crash dump. yes, i do take full responcibility for running -current, just thought i'd share :) Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message