From owner-freebsd-stable@FreeBSD.ORG Sun Apr 24 21:07:42 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFB9F16A4CE for ; Sun, 24 Apr 2005 21:07:42 +0000 (GMT) Received: from melon.pingpong.net (82.milagro.bahnhof.net [195.178.168.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5459143D49 for ; Sun, 24 Apr 2005 21:07:42 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from localhost (localhost.pingpong.net [127.0.0.1]) by melon.pingpong.net (Postfix) with ESMTP id ACF8F4B479; Sun, 24 Apr 2005 23:07:41 +0200 (CEST) Received: from melon.pingpong.net ([127.0.0.1]) by localhost (melon.pingpong.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 00759-02-3; Sun, 24 Apr 2005 23:07:41 +0200 (CEST) Received: from palle.girgensohn.se (1-2-8-5a.asp.sth.bostream.se [82.182.157.66]) by melon.pingpong.net (Postfix) with ESMTP id 76E6D4ADCC; Sun, 24 Apr 2005 23:07:38 +0200 (CEST) Date: Sun, 24 Apr 2005 23:07:38 +0200 From: Palle Girgensohn To: Scott Long Message-ID: In-Reply-To: <426BA8FA.3080602@samsco.org> References: <426BA8FA.3080602@samsco.org> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Scanned: by amavisd-new at pingpong.net cc: stable@freebsd.org Subject: Re: background_fsck=no does not work? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2005 21:07:42 -0000 --On s=F6ndag, april 24, 2005 08.11.06 -0600 Scott Long = wrote: > Palle Girgensohn wrote: >> Hi! >> >> on a 5.4-prerelease machine (dell 2850 dual cpu, running amd64), I have >> this in rc.conf: >> >> fsck_y_enable=3D"YES" >> background_fsck=3D"NO" >> >> >> Still, I'm not certain that fsck is really run at startup. > > Are you expecting a fsck to be run at every startup, regardless of > whether the filesystems are dirty? If so, that is not what these > options do. No, but the machine crashes a lot, sometimes a couple of times in a day=20 (oddly mostly on week-ends, and sometimes it can be stable for a week or=20 two). I'm clueless to what's causing it, but suspect that the amd64 stuff=20 is broken, at least for this machine (dual Xeon). I wanted foreground fsck=20 since I thought there might be a problem with the file systems, but I guess = I was wrong... >> At least, >> running fsck on in multiuser reveals information like below, but perhaps >> that is normal for an active file system? > > Yes, because of the caching effect of the VM layer, the filesystem will > not always be clean. Softupdates (hopefully) means that it will be > consistent and recoverable, but what you're seeing here is normal and > expected. Running foreground-fsck on a mounted filesystem has limited > value, though. OK, I reckoned it was like that. Thanks. >> I'm having stability problems with this machine (it crashes >> sporadically) and I suspect it might have something to do with problems >> in the file system. Could this be true, or is the below stuff completely >> normal? > > You'll need to enable DDB and KDB and post the information from your > crashes. OK, thanks, it's time to dig into that, I guess... /Palle