From owner-freebsd-fs@FreeBSD.ORG Wed Apr 1 19:44:17 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3353D106566C for ; Wed, 1 Apr 2009 19:44:17 +0000 (UTC) (envelope-from fb-fs@psconsult.nl) Received: from mx1.psconsult.nl (psc11.adsl.iaf.nl [80.89.238.138]) by mx1.freebsd.org (Postfix) with ESMTP id B65BD8FC08 for ; Wed, 1 Apr 2009 19:44:16 +0000 (UTC) (envelope-from fb-fs@psconsult.nl) Received: from mx1.psconsult.nl (localhost [80.89.238.138]) by mx1.psconsult.nl (8.14.2/8.14.2) with ESMTP id n31JWr69087846 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 1 Apr 2009 21:32:58 +0200 (CEST) (envelope-from fb-fs@psconsult.nl) Received: (from paul@localhost) by mx1.psconsult.nl (8.14.2/8.14.2/Submit) id n31JWrSU087845 for freebsd-fs@freebsd.org; Wed, 1 Apr 2009 21:32:53 +0200 (CEST) (envelope-from fb-fs@psconsult.nl) Date: Wed, 1 Apr 2009 21:32:53 +0200 From: Paul Schenkeveld To: freebsd-fs@freebsd.org Message-ID: <20090401193253.GA87622@psconsult.nl> Mail-Followup-To: freebsd-fs@freebsd.org References: <49D2F2DE.1090807@bsd.ee> <49D3A177.2040106@goflexitllc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49D3A177.2040106@goflexitllc.com> User-Agent: Mutt/1.5.17 (2007-11-01) Subject: Re: Auto mount and ignore errors 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, 01 Apr 2009 19:44:17 -0000 On Wed, Apr 01, 2009 at 12:16:39PM -0500, Aaron Hurt wrote: > Andrew Brampton wrote: >> 2009/4/1 Andrei Kolu : >> >>> Andrew Brampton wrote: >>> >>>> So my question is, is there a fstab option which will ignore a failed >>>> mount, and if possible continue to boot? I've read the man page, and >>>> did a bit of googling, but didn't find anything. Would there be any >>>> objection to a patch which implemented a "ignerror" flag? >>>> >>> Mount from /etc/rc.local? >> >> You mean create my own script for the mounting? Sure that would work >> but I don't see that as "clean" as placing it in fstab. >> >> Andrew >> > I think "clean" here is a bit misplaced. It's not ever "clean" to ignore a > file system mount error. If you're file system in question is prone to > mount failures it's probably not a good idea to mount it from fstab at all. I use my notebook both in my home office and when visiting customers. When in my office I like to mount some nfs filesystems that are not available when I'm out. Before 7.1 /etc/rc worked just the way I wanted mounting these nfs filesystems when in my office and skipping them with an error telling me that the name of the nfs server cannot be resolved when visiting customers. That old behaviour was clearly wrong as it would also continue booting when really important filesystems cannot be mounted, e.g. due to network problems. However I'd like to argue that there are perfectly legal cases for having filesystems in /etc/fstab that only get mounted when available. So I agree with OP that there should be a clean way of marking some filesystems 'optional' or 'ignerror' in fstab. My 2 cents. Paul Schenkeveld