Red Hat Bugzilla – Bug 127178
automount fails with NIS map entries specifying noquota
Last modified: 2007-11-30 17:10:45 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; IRIX64 IP30; en-US; rv:1.3)
Description of problem:
I have just upgraded my system to Fedora Core 2 and am having
a problem with automount attempting to mount NFS filesystems
from Solaris servers.
The automounter is configured via an NIS map, i.e., it is being
run with the command
/usr/sbin/automount --timeout=60 /home yp home.indirect
All entries in the NIS automount map home.indirect are of the form
This NIS map is being served by a Solaris NIS server over which I
have no control.
When I attempt to automount any such filesystem it fails with a message
written to /var/log/messages saying that noquota is not a valid option
for mounting an NFS file system.
This has always worked in the past for me. I still have a running RedHat
7.3 system that is using the same automount map and has no trouble
automounting these file systems, even with the noquota option in the
NIS automount map entries. If I try to manually mount an NFS filesystem
on that 7.3 machine with the noquota option specified, it fails with a
message that noquota is not supported for NFS, which makes me believe
that somehow the 7.3 automounting system is filtering out the noquota
option before performing the actual mount. It would seem that this
filtering no longer occurs in Fedora 2.
How can I fix this problem without changing the NIS map entries,
which I cannot do?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run automount using an NIS map that specifies noquota as
a mount option for its entries.
2. Attempt to use the automounter to mount a file system specified
by one of these entries.
Actual Results: After the attempt, /var/log/messages will contain a
Jul 2 20:57:11 ctrobot automount: >> Unsupported nfs mount
Expected Results: The filesystem should have been mounted.
The problem is that mount actually regressed, and did not support the
-s option (sloppy mounts). See bug 122448.
*** This bug has been marked as a duplicate of 122448 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.