From owner-freebsd-questions@FreeBSD.ORG Wed Jul 26 13:22:59 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 B43AD16A4DF for ; Wed, 26 Jul 2006 13:22:59 +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 9015343D5F for ; Wed, 26 Jul 2006 13:22:57 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend3.internal (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id 8D49AD91554 for ; Wed, 26 Jul 2006 09:22:56 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by frontend3.internal (MEProxy); Wed, 26 Jul 2006 09:23:00 -0400 X-Sasl-enc: Kj+SYr61CTz0d/C9dvi0mwIw1mRiERVVoH3rYGjdyJVN 1153920176 Received: from [192.168.1.2] (bb-87-81-140-128.ukonline.co.uk [87.81.140.128]) by mail.messagingengine.com (Postfix) with ESMTP id 490DBC653 for ; Wed, 26 Jul 2006 09:22:55 -0400 (EDT) From: RW To: freebsd-questions@freebsd.org Date: Wed, 26 Jul 2006 14:22:51 +0100 User-Agent: KMail/1.9.3 References: <20060726001010.GE29366@tigger.digitaltorque.ca> <20060726010334.GB70646@dan.emsphone.com> In-Reply-To: <20060726010334.GB70646@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607261422.52997.list-freebsd-2004@morbius.sent.com> Subject: Re: fsck in the background 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: Wed, 26 Jul 2006 13:22:59 -0000 On Wednesday 26 July 2006 02:03, Dan Nelson wrote: > In the last episode (Jul 25), Michael P. Soulier said: > > A while ago there was a power failure in my house, long enough to > > wear down the UPS. I had to power-on my server when I got home > > (crappy bios), and I noticed after I logged-in that fsck was running > > non-interactively in the background. > > > > Question: If it finds problems that require administrator > > intervention, how does it tell me if it's running in the background? > > It logs an error to syslog, and the next time you reboot it forces a > foreground check so it can prompt you for instructions. Although to the best of my knowledge, I've never actually seen that happen. What I see is usually the background check works, occasionally the preliminary fsck -F will fail. IIRC that leaves me in single user mode, with instructions to fsck the partition manually.