From owner-freebsd-current Sun Sep 20 02:17:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15071 for freebsd-current-outgoing; Sun, 20 Sep 1998 02:17:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (sf3-44.ppp.wenet.net [206.15.84.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15066 for ; Sun, 20 Sep 1998 02:17:10 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with SMTP id CAA19724; Sun, 20 Sep 1998 02:18:10 -0700 (PDT) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sun, 20 Sep 1998 02:18:09 -0700 (PDT) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org To: Terry Lambert cc: eivind@yes.no, Julian Elischer , Don.Lewis@tsc.tdk.com, current Subject: Re: softupdates & fsck In-Reply-To: <199809200900.CAA12457@usr06.primenet.com> 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 On Sun, 20 Sep 1998, Terry Lambert wrote: [...] > Since I assume that a fsck was done because the clean bit was not > set when the reboot occurred, you are telling me that you needed > two fsck's. Or you are telling me that you trieed to fsck a > mounted FS, which is a no-no. System (most likely only the console) froze, hit reset, fsck ran because the clean bit wasn't set, undeletable directories remained. Rebooted into single user mode, manually ran fsck -y which cleared the problem (or appeared to). I've also had problems with odd undeletable files, which I just booted into single user mode and clri'd (with the same kernel). > Was soft updates enabled? Yes, on both sd0 and 1. > Hitting the reset is no different than going into the debugger. The > disk should be in a consistent state, barring cylinder group bitmaps. > > This assumes your pre-CAM version wasn't so pre-CAM that the sync(2) > issues had yet to be addressed (ie: you would need code dates, and > I would have to ask Julian, or you could ask Julian, to find out > if that date was pre or post the sync(2) fixes). Well, the kernel was built ~Sept 12th. I've cvsup'd numerous times since then so I don't have exact RCS IDs. If I can build a non CAM kernel some way to test this, I'd do it. But I'm somewhat leery of building a CAMified kernel as this has proven itself to be bad idea when combined with softupdatse. > In any case, under no circumstances should the disks be in a > state that results in files in lost+found if soft updates is > working. Good to see I'm not loosing my mind (yet). - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message