From owner-freebsd-fs@FreeBSD.ORG Fri Mar 2 14:45:43 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 4451816A408 for ; Fri, 2 Mar 2007 14:45:43 +0000 (UTC) (envelope-from mwest@cs.uct.ac.za) Received: from mx-out.cs.uct.ac.za (mx-out.cs.uct.ac.za [137.158.96.39]) by mx1.freebsd.org (Postfix) with ESMTP id DDF3E13C4AC for ; Fri, 2 Mar 2007 14:45:42 +0000 (UTC) (envelope-from mwest@cs.uct.ac.za) Received: from mwest by casper2.cs.uct.ac.za with local (Exim 4.42 (FreeBSD)) id 1HN8Ze-000KbB-D4; Fri, 02 Mar 2007 16:17:30 +0200 Date: Fri, 2 Mar 2007 16:17:30 +0200 From: Matthew West To: freebsd-fs@freebsd.org Message-ID: <20070302141730.GA78630@cs.uct.ac.za> References: <45E581DF.4070706@freebsd.org> <629647.7934.qm@web51004.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <629647.7934.qm@web51004.mail.yahoo.com> User-Agent: Mutt/1.4.2.1i Cc: Jason Arnaute Subject: Re: 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: Fri, 02 Mar 2007 14:45:43 -0000 On Wed, Feb 28, 2007 at 08:18:21AM -0800, Jason Arnaute wrote: > But you're right - it's not exactly what I want ... > provided that the critical filesystems are already > clean (all I have are /, /var, and (bulk_data)) I wish > it would just come up and say: > > "if they're clean, mount them and be happy. If > they're not, just _don't mount them_. Just don't do > anything. You've got your / and /var, so just be > happy and wait for someone to manually bring up > (bulk_data)" A cheap-and-nasty way would be to add the "noauto" option for your "(bulk_data)" in /etc/fstab, and then do something like put "mount (bulk_data)" into /etc/rc.local. If the "(bulk_data)" FS is clean, it'll get mounted at boot time. If it's dirty, mount will output an error to console, but the system will be unaffected otherwise. You could even have it fallback to mounting "(bulk_data)" as read-only if you required such a thing. -- mwest@cs.uct.ac.za