Date: Tue, 13 Feb 2007 12:24:03 +0000 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: Tillman Hodgson <tillman@seekingfire.com> Cc: freebsd-questions@freebsd.org Subject: Re: Mounting multiple NFS shares to the same point Message-ID: <45D1ADE3.1010802@dial.pipex.com> In-Reply-To: <20070212194728.GE543@seekingfire.com> References: <20070212170553.GA543@seekingfire.com> <54db43990702121104x7aea5f53tab517d32e85c9b19@mail.gmail.com> <20070212194204.GD543@seekingfire.com> <20070212194728.GE543@seekingfire.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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...).
(local gzip)
sbin/dump $LEVEL -a -C 64 $CHECKPOINT $UPDATE $UPDATEFILE -f -
$filesystem | \
gzip -9 | \
/usr/local/bin/ssh -z -i ${keyfile}
(remote gzip)
/sbin/dump $LEVEL -a -C 64 $CHECKPOINT $UPDATE $UPDATEFILE -f -
$filesystem | \
/usr/local/bin/ssh -z -i ${keyfile} \
"umask 337; gzip -9 > /backup/$ii"
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.
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.
--Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45D1ADE3.1010802>