From owner-freebsd-current Sun Sep 20 02:01:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12988 for freebsd-current-outgoing; Sun, 20 Sep 1998 02:01:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12983 for ; Sun, 20 Sep 1998 02:01:25 -0700 (PDT) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id CAA23797; Sun, 20 Sep 1998 02:00:59 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd023792; Sun Sep 20 02:00:57 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id CAA12457; Sun, 20 Sep 1998 02:00:52 -0700 (MST) From: Terry Lambert Message-Id: <199809200900.CAA12457@usr06.primenet.com> Subject: Re: softupdates & fsck To: garbanzo@hooked.net (Alex) Date: Sun, 20 Sep 1998 09:00:52 +0000 (GMT) Cc: tlambert@primenet.com, eivind@yes.no, Don.Lewis@tsc.tdk.com, current@FreeBSD.ORG In-Reply-To: from "Alex" at Sep 19, 98 01:45:32 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I had to hit reset once, while building world, as my box froze while > logging out of X. End result was fsck grok'd both disks (Quantum, SCSI), > and stuff was left in lost+found for both disks. The one with /usr/obj > had some dirs (and files too I think) that couldn't be rm -rf'd. Going > into single user mode, and manually running fsck on the damaged drive > seemed to fix this. And, this was with a pre-cam kernel, with no patches > or anything. > > Perhaps a related problem? 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. Was soft updates enabled? 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). 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. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message