From owner-freebsd-questions@FreeBSD.ORG Tue Feb 13 14:38:50 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1420916A400 for ; Tue, 13 Feb 2007 14:38:50 +0000 (UTC) (envelope-from tillman@seekingfire.com) Received: from mail.seekingfire.com (caliban.seekingfire.com [24.89.83.8]) by mx1.freebsd.org (Postfix) with ESMTP id 7DAF013C494 for ; Tue, 13 Feb 2007 14:38:49 +0000 (UTC) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 96DA0371; Tue, 13 Feb 2007 08:38:48 -0600 (CST) Date: Tue, 13 Feb 2007 08:38:48 -0600 From: Tillman Hodgson To: freebsd-questions@freebsd.org Message-ID: <20070213143848.GH543@seekingfire.com> References: <20070212170553.GA543@seekingfire.com> <54db43990702121104x7aea5f53tab517d32e85c9b19@mail.gmail.com> <20070212194204.GD543@seekingfire.com> <20070212194728.GE543@seekingfire.com> <45D1ADE3.1010802@dial.pipex.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45D1ADE3.1010802@dial.pipex.com> X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/personal/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers X-Tillman-rules: yes he does User-Agent: Mutt/1.5.13 (2006-08-11) Subject: Re: Mounting multiple NFS shares to the same point 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: Tue, 13 Feb 2007 14:38:50 -0000 On Tue, Feb 13, 2007 at 12:24:03PM +0000, Alex Zbyslaw wrote: > Tillman Hodgson wrote: > > >If that still holds true in the -current src, the second mount will > >*definitely* cause me backup problems. I may have to move to keeping the > >NFS export always mounted, which is not ideal. > > Could you use something like ssh to transfer the files rather than > needing NFS? (I don't know if you mentioned what the NFS-end box was...). That's a good idea. In this case the NFS-end box is an Infrant appliance so I don't think I can use scp. I'll check deeper into it -- if it can do scp, that gives me more options. > I'm also not clear why you think that keeping the NFS partition mounted > all the time is so bad. If there is no access then surely the overhead > is minimal. That's true, there's no real performance hit. It's not the overhead I'm worried about, it's minimizing the exposure of the backups volume to problems. A network filesystem that isn't mounted is one that's much harder to accidently rm files from and such :-) > Your other alternative is to use lockfiles to control when things get > mounted/unmounted. If the control file is locked, you wait until it's > unlocked (or bomb with an error, whatever). Trivial in perl, and > lockf(1) looks like the way to go with shell. That's the scripting magic that I mentioned. It looks like this is likely the best solution with my current volume arrangement. In hindsight, I think should've used three shares instead of one and then the daily, weekly and monthly mounts wouldn't conflict with each other. -T -- You cannot manipulate a marionette with only one string. - The Zensunni Whip