All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Sahlender <rsahlen@voicenet.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: autofs@linux.kernel.org
Subject: Re: multiple servers per automount
Date: Wed, 8 Oct 2003 16:43:04 -0400	[thread overview]
Message-ID: <20031008204304.GA4056@born2.midworld.org> (raw)
In-Reply-To: <3F845E0C.7020801@zytor.com>

On Wed, Oct 08, 2003 at 11:57:16AM -0700, H. Peter Anvin wrote:
> Rich Sahlender wrote:
> > This is probably a faq but I havn't seen it asked in recent months...
> > 
> > I have a situation where two network appliance filers with identical
> > file systems are used to serve read only mounts for CAD software tools.
> > Both Solaris and HP-UX support an automount like:
> > 
> > cadtool	-ro	tools1,tools2:/vol/vol1/tools/&
> > 
> > and will automatically switch to the other server if the initial mount
> > becomes unavailable.
> > 
> > Last time I was able to check Linux autofs did not support the failover
> > and complained about the syntax. Has this changed or are there plans to
> > support the syntax above with failover for read only mounts?
> > 
> 
> This should not be an autofs feature but an NFS feature, for obvious
> reasons: it's equally applicable for static mounts.
> 
> Furhtermore, failover HAS to be done at the NFS layer.
> 
> The fact that Slowlaris does it in autofs is not a good motivation --
> it's idiotic design.
> 
> 	-hpa

I disagree. These are read only mounts. How is it an idiotic design to
provide a little extra availability by switching to another server in the
list if the mounted server becomes unavailable?

Furthermore, the fact that it is equally applicable for static mounts
does not make it an obvious NFS issue. I submit it's both an NFS and an
autofs issue...

  reply	other threads:[~2003-10-08 20:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-08 17:24 multiple servers per automount Rich Sahlender
2003-10-08 18:57 ` H. Peter Anvin
2003-10-08 20:43   ` Rich Sahlender [this message]
2003-10-08 21:28   ` Mike Waychison
2003-10-09  3:07     ` Ian Kent
2003-10-09 18:23       ` Mike Waychison
  -- strict thread matches above, loose matches on Subject: below --
2003-10-09 18:45 Ogden, Aaron A.
2003-10-09 19:00 ` Mike Waychison
2003-10-10  1:08   ` Ian Kent
2003-10-09 21:20 Ogden, Aaron A.
2003-10-09 21:36 ` Mike Waychison
2003-10-10  1:16   ` Ian Kent
2003-10-10  1:15 ` Ian Kent
2003-10-09 22:07 Ogden, Aaron A.
2003-10-10 15:16 Ogden, Aaron A.

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=20031008204304.GA4056@born2.midworld.org \
    --to=rsahlen@voicenet.com \
    --cc=autofs@linux.kernel.org \
    --cc=hpa@zytor.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.