From owner-freebsd-fs@FreeBSD.ORG Wed Feb 28 05:44:25 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6436316E647 for ; Wed, 28 Feb 2007 05:44:24 +0000 (UTC) (envelope-from non_secure@yahoo.com) Received: from web51014.mail.yahoo.com (web51014.mail.yahoo.com [206.190.39.79]) by mx1.freebsd.org (Postfix) with SMTP id 181EF13C441 for ; Wed, 28 Feb 2007 05:44:23 +0000 (UTC) (envelope-from non_secure@yahoo.com) Received: (qmail 45809 invoked by uid 60001); 28 Feb 2007 05:17:42 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=44cX90bXOQ+u8ML6qbNCR72RbY4DW8pGYLUImt0Ol//msYBeeH142iMaoxtmuHeJ937dVx3JBgbrBWkA1UGKryjHgxFS9abEWL1MFR2E/ehjr0Q/ApXamOdZH5eLv0PkrHU71lrJKzSmnhu3NVIgMz23V26D6U70MZUUlWYV5hs=; X-YMail-OSG: IPkGbokVM1n7FLuYuHTpGCCz.BGxZxDuMy7tyPTTreWEUzCGO8kvh9VdC_ktEZSyJtT246TdlSjGlsiEZh6IvgyUDmHzJBBYm8ldUXV41YUMdvUbTzI9HVNAX8JCBZH_j5_vA.4luT0_bwMjHl.y17fM Received: from [75.72.230.91] by web51014.mail.yahoo.com via HTTP; Tue, 27 Feb 2007 21:17:42 PST Date: Tue, 27 Feb 2007 21:17:42 -0800 (PST) From: Jason Arnaute To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <660490.45660.qm@web51014.mail.yahoo.com> X-Mailman-Approved-At: Wed, 28 Feb 2007 12:48:49 +0000 Subject: Looking for a graceful way to disable BG fsck ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 05:44:27 -0000 I do not particularly like to do a BG fsck - it takes forever and the system is near unusable while it goes ... and I don't mind just taking it down for a little while to get it over with. However, if I set the system: background_fsck="no" Then I have to wait for all mounts to fsck before the system will even come up on the network in a multi-user fashion. So what I am doing now is, if I have to reset a hung server, I quick race to log in, like an idiot, and hopefully log in and comment out the filesystems in fstab before 60 seconds expires and the bg fscks start. Because if I miss it, I'm screwed - you can't kill a BG fsck, and you can't reboot the system while a BG fsck is going on. So then you have to reset it again, which is scary because you've got a dirty filesystem, while being fsck'd, and then you dirty it up some more. So one plan is to just leave the non-root filesystems commented in /etc/fstab all the time, but that's not nice because if you ever need to legitimately (gracefully, on purpose) reboot, then they don't come up. Bleah. So my question is this: Is there any nice, elegant way to tell my system: "If everything is clean, then mount it all up and go. But if a non-root filesystem is not clean, just skip it altogether and boot up into multiuser mode and I will log in and fsck it manually. But under no circumstances will you BG fsck anything." Any way to do that ? ____________________________________________________________________________________ Need a quick answer? Get one in minutes from people who know. Ask your question on www.Answers.yahoo.com