Bug 122448

Can you manually mount that share with the nobrowse option?

My current workaround for my home directory is to:

shutdown autofs
mkdir -p /home/clahti
mount 192.168.51.16:/export/sc5_2/home/clahti /home/clahti

that works.

mount -nobrowse santaclara7:/export/tools/config /mnt/test

results in "Unsupported nfs mount option: browse"

mount santaclara7:/export/tools/config /mnt/test

results in successful mount

We are not using the nobrowse option anywhere, either NFS server or
client that I can find.

could you post your auto.master, and the map file for /tools?

Thanks!

here you go:

[clahti@lnclahti ~]$ cd /etc
[clahti@lnclahti /etc]$ cat auto.master
#
# $Id: auto.master,v 1.3 2003/09/29 08:22:35 raven Exp $
#
# Sample auto.master file
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# For details of the format look at autofs(5).
#/misc  /etc/auto.misc --timeout=60
#/misc  /etc/auto.misc
#/net   /etc/auto.net


[root@scadmin maps]# cat auto.tools
*     santaclara7:/export/sc7_1/tools/&/$OSNAME

There is no entry for auto.tools in there.  How about sending along
the results of:

ypcat auto.master

Thanks!

Here you go:

[clahti@lnclahti /etc]$ ypcat auto.master
auto.tools       -nobrowse,timeo=120,int,retrans=6
auto.archive     -nobrowse,timeo=120,int,retrans=6
auto.projects    -nobrowse,timeo=120,int,retrans=6
auto.home        -nobrowse,timeo=120,int,retrans=6
auto.proj_mm8    -nobrowse,timeo=120,int,retrans=6
auto.proj_arm333 -nobrowse,timeo=120,int,retrans=6
auto.groups      -nobrowse,timeo=120,int,retrans=6
auto.proj_mm7    -nobrowse,timeo=120,int,retrans=6

doh! I see the -nobrowse option now, but apparently this works for all
RH up to FC1, as well as Solaris and HPUX.

A bit more clarification on the map syntax, the &/$OSNAME portion
allows us to  mount a tool with the identical client side path from
Linux, Solaris or HPUX, but have different physical binaries, for example

logical path
/tools/cadence/bin

physical path = 
Linux: santaclara7:/export/sc7_1/tools/cadence/Linux/bin
SunOS: santaclara7:/export/sc7_1/tools/cadence/SunOS/bin
HPUX: santaclara7:/export/sc7_1/tools/cadence/HPUX/bin

so I should say that

mount santaclara7:/export/tools/config/Linux /mnt/test

successfully mounts, but this should not pose a problem...

Ahh, I see.  nobrowse is a solaris automount option.  See below for
the excerpt from their man page.

I agree that this is a bug.  It looks like the older autofs passed the
-s option to mount (sloppy).  This allowed for mount to succeed even
if the options specified were not supported by the filesystem.

I'll work on fixing this in the newest autofs.

Thanks!

Jeff


====================================================================
Browsing
     The Solaris 2.6 release supports  browsability  of  indirect
     maps.  This  allows  all of the potential mount points to be
     visible, whether or not they  are  mounted.  The   -nobrowse
     option can be added to any indirect
      autofs map to disable browsing. For example:

     /net     -hosts      -nosuid,nobrowse
     /home    auto_home

     In this case, any hostnames would only be visible  in   /net
     after they are mounted, but all potential mount points would
     be  visible  under  /home.   The   -browse  option   enables

SunOS 5.9            Last change: 1 Nov 1999                    7

System Administration Commands                      automount(1M)

     browsability  of   autofs  file systems. This is the default
     for all indirect maps.
====================================================================

It turns out that we removed support for sloppy mounts for nfs in our
version of mount.  This is not desirable and should be fixed.

The upstream 2.12 sources still support sloppy in nfsmount.c.  The
patch which removes this is: util-linux-2.11z-01-nfs.patch.

The section of code we're interested in here is in mount/nfsmount.c:

    } else {
        if (!sloppy) {
            printf(_("unknown nfs mount option: "
                     "%s%s\n"), val ? "" : "no", opt);
            goto fail;
        }
    }

*** Bug 124305 has been marked as a duplicate of this bug. ***

This was fixed in util-linux-2.12-18 (which got into FC2).

Actually, I don't think it is fixed. We are still seeing this with
automounts with quota/noquota options for Solaris, with a fresh
install of FC2.
Note that the patch above refers to "unknown nfs mount option: "
whereas the error I get is "Unsupported nfs mount option:"

I agree with Michael.  Something is still broke with FC2. With a stock
FC2 install we are seeing the  "Unsupported nfs mount option:"  for
the "quota/noquota/grpid, etc..." options on mounts generated from
Solaris & Irix systems.

Created attachment 100665 [details]
possible patch

I think the problem is in the code added in the util-linux-2.11z-01-nfs.patch
patch to mount/nfsmount.c . In the parse_options subroutine, the code is just
dropping through to the bad_options: tag, and dropping out there. We probably
want something like this (at the moment untested) patch.

Ahh, indeed.  My fault for looking at the wrong case.  This patch
looks reasonable to me.  Thanks for taking the time to look into it!

-Jeff

I have now built an rpm with my patch applied, and it seems to fix the
problem for me at least.

*** Bug 124983 has been marked as a duplicate of this bug. ***

I'm going to incorporate this patch into the upcoming 2.12a-1 package.
Thanks!

This big has been "closed rawhide", but the available util-linux
package is still the buggy one.

Could you make the resolution true? :)

Also, could you pick up the selinux patches in bug #126720?

Thanks!

From what I can see, to get things working again, you need to grab two
parts:

(1) A fix to util-linux (grab util-linux-2.12a-2.i386.rpm from the
development area) is necessary to make the mount -s option work again.

(2) A fix to autofs (grab autofs-4.1.3-8.i386.rpm from the development
area) is also apparently necessary to make autofs use the -s option
again. (And of course, this requires numerous dependency updates -- bleh.)

All version of autofs use the -s option.  You only need (1) above.

-Jeff

It would be nice to see both in errata to FC, but this is probably
below errata priority. You can use the fixed rpms from ATrpms, no
further dependencies than the two rpms:

http://ATrpms.net/name/autofs/
http://ATrpms.net/name/util-linux/

Tested with fc1.

*** Bug 127178 has been marked as a duplicate of this bug. ***

This problem is back again in the current rawhide package (2.12a-10).

The patch I suggested in #13 still fixes the problem for me when
applied to 2.12a-10.

Looks like a hunk got dropped during a patch merge. SteveD is fixing.
Thanks for keeping us posted!

This problem is critical for us! We can't upgrade dozens of machines.
Please make this an errata update.

It was fixed in rawhide as of 2.12a-11 (and I verified the fix in that
version on an FC2 host).