From: Peter Staubach <staubach@redhat.com>
To: chuck.lever@oracle.com
Cc: nfs@lists.sourceforge.net
Subject: Re: mount.nfs: chk_mountpoint()
Date: Thu, 23 Aug 2007 16:12:30 -0400 [thread overview]
Message-ID: <46CDEA2E.10902@redhat.com> (raw)
In-Reply-To: <46CDE76C.3040800@oracle.com>
Chuck Lever wrote:
> Peter Staubach wrote:
>> But your explanation makes sense, although we should be moving
>> people away from static mounts in fstab and towards dynamic
>> mounting via autofs. Ian and Jeff have made autofs much, much
>> better in recent times. Improving autofs further to make it
>> only mount file systems which are actually referenced would make
>> it even better.
>
> I'm in great favor of autoconfiguration. Anything that will make NFS
> "just work" is goodness, in my book.
>
Is this an argument for or against autofs or these changes?
>> How do we find out whether we need to continue supporting this
>> semantic or whether we can do away with it? Clearly, if it was
>> busted, then not many people were depending upon it because
>> there didn't seem to be any hue and cry about it not working.
>
> Well, that change went into nfs-utils in May of 2007, only 3 months
> ago. Depending on when nfs-utils-1.1.0 got into Fedora 7, I don't
> think the change has had wide exposure quite yet.
>
> Considering there hasn't been much "hue and cry" about "bg" not
> working in Fedora, however, that may not be much of a standard by
> which to measure customer dissatisfaction.
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.
A much better solution to the problem was autofs because it
delayed the mounting until the file system was actually needed.
The "bg" option can lead to applications not working correctly
because the file system may or may not be mounted when they
need it to be there and there is no automatic synchronization
to block them until it is. Autofs supplies this synchronization,
thus once again, making it a vastly superior solution.
Thanx...
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-23 20:12 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 [this message]
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
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=46CDEA2E.10902@redhat.com \
--to=staubach@redhat.com \
--cc=chuck.lever@oracle.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.