From: Peter Staubach <staubach@redhat.com>
To: Frank van Maarseveen <frankvm@frankvm.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: mount.nfs: chk_mountpoint()
Date: Thu, 30 Aug 2007 07:53:32 -0400 [thread overview]
Message-ID: <46D6AFBC.3000208@redhat.com> (raw)
In-Reply-To: <20070830101249.GA9880@janus>
Frank van Maarseveen wrote:
> On Thu, Aug 23, 2007 at 04:12:30PM -0400, Peter Staubach wrote:
>
>> I would guess that not so many people are using the "bg" option,
>> period. Many of Linux's customers are ex-Sun customers and they
>> were educated to use autofs and to move away from and stay away
>> from static mounts via fstab or vfstab.
>>
>> The "bg" option was a hack added to speed up system booting.
>>
>
> No, it is indispensable to recover properly from a power outage:
> servers tend to boot slower than clients. Also, it is not unusual to
> have some minor network/server problems after an outage causing the
> mount to fail.
>
> Without the bg option a temporary power outage may render all client
> systems unusable.
And a better solution to this problem is still to use autofs.
That said, what use are the clients _until_ the servers are up?
The applications on them can't run correctly because the file
systems that they depend upon may or may not be there yet. With
autofs, you would have a chance of getting the synchronization
right.
You also get all sorts of benefits such as decreased resource
usage (by not having inactive file systems mounted), reduced
hangs (by not having inactive file systems from servers which
go down still mounted), in addition to the situation described
above and other benefits as well.
I do recognize that we can't get rid of the bg option, but I
would request that people using it consider different alternatives
to solving their problems.
ps
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-08-30 11:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 19:02 mount.nfs: chk_mountpoint() Chuck Lever
2007-08-23 12:50 ` Peter Staubach
2007-08-23 17:45 ` Chuck Lever
2007-08-23 18:22 ` Peter Staubach
2007-08-23 20:00 ` Chuck Lever
2007-08-23 20:12 ` Peter Staubach
2007-08-23 20:30 ` Chuck Lever
2007-08-23 20:49 ` Peter Staubach
2007-08-30 10:12 ` Frank van Maarseveen
2007-08-30 11:53 ` Peter Staubach [this message]
2007-08-30 16:01 ` Chuck Lever
2007-08-30 16:07 ` Peter Staubach
2007-08-30 16:18 ` Chuck Lever
2007-08-30 19:15 ` Talpey, Thomas
2007-08-30 21:11 ` Peter Staubach
2007-08-30 16:19 ` J. Bruce Fields
2007-08-30 16:24 ` Chuck Lever
2007-08-30 16:16 ` Frank van Maarseveen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46D6AFBC.3000208@redhat.com \
--to=staubach@redhat.com \
--cc=frankvm@frankvm.com \
--cc=nfs@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.