Hi.

On Mon, 09 Jan 2017 08:14:51 -0500
Harry Putnam <rea...@newsguy.com> wrote:

> Reco wrote:
> > Note that it be simplified to:
> >
> > *     --fstype=nfs4,rw,soft,intr    191.168.1.42:/projects/&
> 
> I created /etc/auto.nfs and tried that forumulation. Restarted
> autofs.  Nothing gets mounted under (now simplified to /projects in
> auto.master) /projects when I do ls /projects/d0 or /projects/dv
> 
> There is a bit of a pause with `ls /projects/dv (or d0) but then I
> get:
>   ls: cannot access /projects/dv: No such file or directory

Won't it be fun otherwise?

The good thing is - autofs is working as intended.
The bad thing is - mount is failing.

Which brings me to this:

1) What security option are you using (i.e. none, sys, krb5, etc)?
If unsure, please mount a share by hand and obtain mount options
from /proc/mounts.

2) If you're using kerberos, can autofs access krb5.conf and
krb5.keytab?

3) Stop autofs, start it like this:

/usr/sbin/automount -fd

Mount a filesystem. Watch the debug output. Terminate it with Ctrl+C.

 
> One question... am I supposed to create the directories
> /projects/dv /projects/d0 ?
> 
> It appears from the instructions I've seen that .. no I am not to
> create those dir... just /projects/.  however, I did try it both ways
> and can report that nothing gets mounted in either test.

No, you definitely do not. Either autofs creates a directory for you, or
you're unable to mount it. Top-level directory *must* be created, but
you did it.

 
> > Also please note that they give you /etc/auto.net just for your case
> > (i.e. mounting nfs).
> 
>  Not sure what you mean by `give you'. Do you mean to use as is?
>  I tried:
>    root # grep -v '^#\|^$' /etc/auto.master
>    /projects     /etc/auto.net   --timeout=180  (Note: It now says `auto.net')
>    +dir:/etc/auto.master.d
>    +auto.master

Should be something like this:

/projects program:/etc/auto.net --timeout=180


>  Made sure auto.net is chmod 755

Yep, it's importanet.


>  Changed (in auto.net)
>   opts="-fstype=nfs,hard,intr,nodev,nosuid"
>   #opts="-fstype=nfs4,hard,intr,nodev,nosuid,async"
>  To:
>   #opts="-fstype=nfs,hard,intr,nodev,nosuid"
>   opts="-fstype=nfs4,hard,intr,nodev,nosuid,async"

A small nit. Do not use 'hard' mount option unless you absolutely need
it. It is painful, and it's by design. It has nothing to do with your
current problem, though. What you probably need is:

-fstype=nfs4,soft,intr,nodev,nosuid,async

Reco

Reply via email to