mount fails because entry in multi-mount doesn't work

mount fails because entry in multi-mount doesn't work

[Tom Georgoulias]

Yesterday I ran into an issue where a mount point wasn't working and 
tracked it down to one of the submounts.  From what I can tell, if one 
of the submounts in a multi-mount doesn't work, the entire mount point 
won't work.  If that is the case, can this behavior be changed?

System:
Sun V20Z running RHEL3 WS AMD64, 2.4.21-15ELsmp (with 
kernel-smp-unsupported-2.4.21-15.EL RPM to get autofs4 module) and 
autofs-4.1.2-6 from Jeff Moyer.


[root@winston root]# cd /proj/tec/layout/copperhead
-bash: cd: /proj/tec/layout/copperhead: No such file or directory

Checked the messages:

[root@winston root]# tail /var/log/messages
May 12 17:22:47 winston automount[8314]: rm_unwanted: 
/proj/tec/layout/maskprep1
May 12 17:22:47 winston automount[8314]: rm_unwanted: 
/proj/tec/layout/copperhead
May 12 17:22:47 winston automount[8314]: rm_unwanted: /proj/tec/layout
May 12 17:22:47 winston automount[6941]: attempting to mount entry 
/proj/tec/layout
May 12 17:22:47 winston automount[8318]: >> mount: 
macduff:/fsys/fs04/maskprep1 failed, reason given by server: Permission 
denied
May 12 17:22:47 winston automount[8318]: mount(nfs): nfs: mount failure 
macduff:/fsys/fs04/maskprep1 on /proj/tec/layout/maskprep1
May 12 17:22:47 winston automount[8318]: failed to mount /proj/tec/layout
May 12 17:22:47 winston automount[8318]: rm_unwanted: 
/proj/tec/layout/maskprep1
May 12 17:22:47 winston automount[8318]: rm_unwanted: 
/proj/tec/layout/copperhead
May 12 17:22:47 winston automount[8318]: rm_unwanted: /proj/tec/layout

Noticed how mount failed for /proj/tec/layout/maskprep1, then the whole 
/proj/tec/layout mount fails.  The mount point it was failing on is 
intentionally unshared at the moment, so I'm not surprise it couldn't 
make it. Took the entry out of the automount map

layout \
/copperhead eclipse0:/export/layout/copperhead \
/maskprep1 macduff:/fsys/fs04/maskprep1 \
<snip>

refreshed the automount daemon's cache.  Mount works now.

[root@winston root]# pkill -HUP -f auto.proj
[root@winston root]# cd /proj/tec/layout/copperhead
[root@winston copperhead]# ls
mpc5554.0l00x  mpc5554.0l87p  restore
[root@winston copperhead]#

Tom
-- 
Tom Georgoulias
POPI Classification
[x] General Business Information
[] Freescale Semiconductor Internal Use
[] Freescale Semiconductor Confidential Proprietary

Re: mount fails because entry in multi-mount doesn't work

[raven]

On Thu, 13 May 2004, Tom Georgoulias wrote:

> Yesterday I ran into an issue where a mount point wasn't working and 
> tracked it down to one of the submounts.  From what I can tell, if one 
> of the submounts in a multi-mount doesn't work, the entire mount point 
> won't work.  If that is the case, can this behavior be changed?

Use the -nonstrict option on the autofs mount.

OK this has happened one to many times. I think I'm going to change this 
default.

What do people think about this idea?

Ian

Re: mount fails because entry in multi-mount doesn't work

[Taylor, ForrestX]

On Thu, 2004-05-13 at 08:08, raven@themaw.net wrote:
> On Thu, 13 May 2004, Tom Georgoulias wrote:
> 
> > Yesterday I ran into an issue where a mount point wasn't working and 
> > tracked it down to one of the submounts.  From what I can tell, if one 
> > of the submounts in a multi-mount doesn't work, the entire mount point 
> > won't work.  If that is the case, can this behavior be changed?
> 
> Use the -nonstrict option on the autofs mount.
> 
> OK this has happened one to many times. I think I'm going to change this 
> default.
> 
> What do people think about this idea?

Yes, please!  I have been asking for this default for years.

Forrest

Re: mount fails because entry in multi-mount doesn't work

[Tom Georgoulias]

raven@themaw.net wrote:

> Use the -nonstrict option on the autofs mount.

Any docs for this?  I didn't see anything in the man pages about 
nostrict and I wasn't able to get it to work, so I want to be sure I've 
done everything correctly.

[root@winston root]# /sbin/service autofs status
Configured Mount Points:
------------------------
/usr/sbin/automount --timeout=60 --debug /proj/tec yp auto.proj 
-rw,hard,intr,nosuid,nostrict rsize=32768,wsize=32768

<snipped>

Active Mount Points:
--------------------
/usr/sbin/automount --timeout=60 --debug /proj/tec yp auto.proj 
-rw,hard,intr,nosuid,nostrict rsize=32768,wsize=32768

<snipped>

[root@winston root]# cat /etc/auto.master
# /etc/auto.master
yp:auto_master
/home yp:auto.home
[root@winston root]# ypcat -k auto_master | grep auto.proj
/proj/tec auto.proj             -rw,hard,intr,nosuid,nostrict

-- 
Tom Georgoulias
POPI Classification
[x] General Business Information
[] Freescale Semiconductor Internal Use
[] Freescale Semiconductor Confidential Proprietary

Re: mount fails because entry in multi-mount doesn't work

[Jeff Moyer]

==> Regarding Re: [autofs] mount fails because entry in multi-mount doesn't work; Tom Georgoulias <tom.georgoulias@freescale.com> adds:

tom.georgoulias> raven@themaw.net wrote:
>> Use the -nonstrict option on the autofs mount.

tom.georgoulias> Any docs for this?  I didn't see anything in the man pages
tom.georgoulias> about nostrict and I wasn't able to get it to work, so I
tom.georgoulias> want to be sure I've done everything correctly.

Spelling counts. ;)  nonstrict, not nostrict.  Give that a try.
                       ^
-Jeff