On Tue, 2005-02-01 at 15:08 -0500, Jeff Moyer wrote:
> ==> Regarding Re: [NFS] NFS readonly failover and linux?; Ian Kent <[EMAIL 
> PROTECTED]> adds:
> 
> raven> On Mon, 31 Jan 2005, Dan Stromberg wrote:
> >> On Sat, 2005-01-29 at 11:46 +0800, [EMAIL PROTECTED] wrote: > On Thu, 27
> >> Jan 2005, Dan Stromberg wrote:
> >> > 
> >> > >
> >> > > The autofs man pages on Redhat Enterprise Linux 3 as well as Fedora
> >> Core > > 3 both say that autofs supports replicated, readonly fileserver
> >> failover > > - but then there's a footnote of sorts that says autofs
> >> only supports it > > to the extent that mount does.
> >> > 
> >> > That part of the man page is old and slightly out of date.
> >> > 
> >> > The reason that this is left there is that autofs cannot support >
> >> dynamic failover as it just uses mount. However, a different host may be
> >> > selected at mount, after a previous timeout, for example. The issue of
> >> > umounting existing mounts from servers that have gone away is not >
> >> explicitly dealt with yet.
> >> 
> >> I see.
> >> 
> >> > >
> >> > > Upon trying to do such a mount, I get:
> >> > >
> >> > > seki-root> mount > >
> >> dcslib1.nacs.uci.edu,dcslib4.nacs.uci.edu:/dcspdb/rhel-3-i686 /mnt/nfs >
> >> > mount: warning: multiple hostnames not supported > > Thu Jan 27
> >> 16:12:18
> >> 
> >> > What version of autofs are you using?  > The autofs replicated server
> >> code is still relatively new.
> 
> raven> But, as we know, mount doesn't know about multiple host
> raven> names. autofs breaks these out.
> 
> So what is the actual problem, here?  Are you using the automounter?  What
> do your config files look like?
> 
> >> FC3: autofs-4.1.3-28 RHEL3: autofs-4.1.3-47
> 
> raven> I believe that the replicated server code should be present in both
> raven> of these.
> 
> raven> Can you confirm please Jeff?
> 
> raven> Perhaps you are seeing a bug which needs to be addressed.
> 
> Yes, the replicated server code is present in both of these versions.
> 
> >> The FC3 is yum update'd fairly regulary, and the RHEL3 is up2date'd
> >> regularly as well.
> >> 
> >> > If your autofs supports replicated server map entries then multiple >
> >> host mount requests will not reach the mount command.
> >> 
> >> Interesting.
> >> 
> >> > If you are using a RedHat based distro then check >
> >> http://people.redhat.com/jmoyer > for the latest patched versions
> >> > 
> >> > Also, you may need a kernel patch depending on your kernel
> >> version. See > README.patches in the distribution or join the autofs
> >> list at > http://linux.kernel.org/mailman/listinfo/autofs
> >> 
> >> I'm certain my management will only go for this, in the short term, if
> >> it works on a mainstream RHEL3 system.  Unfortunately, for me, the rest
> >> is academic interest.
> 
> raven> Once again I believe that the kernels mentioned here are up to date
> raven> wrt autofs.
> 
> raven> Certainly, the latest FC3 kernel is at 2.6.10 which has all the
> raven> autofs4 updates included in the base kernel.
> 
> raven> I believe the latest update to RHEL3 is also up to date. Jeff?
> 
> Yes, both kernels have the necessary patches to support replicated server.
> 
> raven> So perhaps you could send a log trace with the "--debug" option
> raven> added to the master map entry.
> 
> And please include the contents of your maps!
> 
> -Jeff

Here are the maps we use on Solaris 9.  Should they work the same way on
RHEL 3?

autoinst-strombrg> cat /etc/auto_dcslib
/dcs -ro
dcslib1.nacs.uci.edu,dcslib2.nacs.uci.edu,dcslib3.nacs.uci.edu:/dcspdb/sun4-5
/dcslib -ro
dcslib1.nacs.uci.edu,dcslib2.nacs.uci.edu,dcslib3.nacs.uci.edu:/dcspda

autoinst-strombrg> cat /etc/auto_master
# Master map for automounter
#
+auto.master
/net            -hosts          -nosuid,nobrowse
#/home          auto_home       -nobrowse
/xfn            -xfn
/-             auto_direct


Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
autofs mailing list
[email protected]
http://linux.kernel.org/mailman/listinfo/autofs

Reply via email to