From owner-freebsd-questions@FreeBSD.ORG Fri Mar 17 00:30:55 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B91F016A400 for ; Fri, 17 Mar 2006 00:30:55 +0000 (UTC) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F89743D46 for ; Fri, 17 Mar 2006 00:30:55 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id C74DFD41426 for ; Thu, 16 Mar 2006 19:30:53 -0500 (EST) Received: from frontend3.messagingengine.com ([10.202.2.152]) by frontend1.internal (MEProxy); Thu, 16 Mar 2006 19:30:53 -0500 X-Sasl-enc: MjC7dGpjtp2SQr75a8CyhHiSEhWwuqIjhWYxGM704Ucr 1142555450 Received: from gumby.localdomain (bb-87-81-140-128.ukonline.co.uk [87.81.140.128]) by frontend3.messagingengine.com (Postfix) with ESMTP id 2DC836D9 for ; Thu, 16 Mar 2006 19:30:50 -0500 (EST) From: RW To: freebsd-questions@freebsd.org Date: Fri, 17 Mar 2006 00:30:49 +0000 User-Agent: KMail/1.9.1 References: <3aaaa3a0603142307l5f89dd36n@mail.gmail.com> <20060315073127.GD48583@dan.emsphone.com> In-Reply-To: <20060315073127.GD48583@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200603170030.51491.list-freebsd-2004@morbius.sent.com> Subject: Re: some questions about fsck, loader.conf X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Mar 2006 00:30:55 -0000 On Wednesday 15 March 2006 07:31, Dan Nelson wrote: > > In rc.conf I have enabled fsck_y_enable="YES" to allow unattended > > fsck fixes after improper shutdown but I have noticed there are some > > problems remaining as shown by a read only fsck. Does the above > > switch not fix all problems or is it the case the fsck bootup script > > only does partial tests? > > A read-only fsck of a mounted filesystem will never come back clean, > since the filesystem's mounted :) I think the question was: why did it find an error, when fsck had run at boot? Were you running background checking? And had it completed? Also there was a bug where partitions fixed with background checking still showed a minor error when unmounted and checked - check the list for details.