All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank van Maarseveen <frankvm@frankvm.com>
To: Peter Staubach <staubach@redhat.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: mount.nfs: chk_mountpoint()
Date: Thu, 30 Aug 2007 18:16:38 +0200	[thread overview]
Message-ID: <20070830161638.GA13213@janus> (raw)
In-Reply-To: <46D6AFBC.3000208@redhat.com>

On Thu, Aug 30, 2007 at 07:53:32AM -0400, Peter Staubach wrote:
> 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.

Sometimes, but not always.

> 
> That said, what use are the clients _until_ the servers are up?

The point is, you would have to re-issue mount -a whenever a server
starts to honour mount requests again: manual intervention on all
client systems is not really practical with many clients.

> You also get all sorts of benefits such as decreased resource

No, actually the automounter _costs_ resources depending on the situation:
The automatic umount flushes all kinds of caches on the client, requiring
network bandwith after mounting them again.

There is no perfect solution. autofs and statically configured mounts
have both advantages and disadvantages.

-- 
Frank

-------------------------------------------------------------------------
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

      parent reply	other threads:[~2007-08-30 16:16 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
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 [this message]

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=20070830161638.GA13213@janus \
    --to=frankvm@frankvm.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=staubach@redhat.com \
    /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.