© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Created attachment 555563
Fix auto.net to ignore duplicate export partitions
Description of problem:
For NFS servers which export the same partition with different options (for example, a partition might be exported to one system with root privileges enabled and all other systems with root squash enabled--this is a common scenario in Enterprise environments), the /net automount map fails to find ANY exported partitions.
Version-Release number of selected component (if applicable):
This issue is present in all versions of autofs 4 and autofs 5 that I've checked.
How reproducible:
100%.
Steps to Reproduce:
1. Configure an NFS server to export the same partition in two different ways and export them. When you run showmount -e against that host you should see multiple entries like this:
~$ showmount -e snap-dev01
Export list for snap-dev01:
/user 172.0.0.0/8
/tools 172.0.0.0/8
/projects 172.0.0.0/8
/user devtools
/tools devtools
/projects devtools
The server doesn't have to be running Red Hat (or even Linux); it's not a server problem.
2. On a client (running Red Hat), attempt to access one of these partitions through the /net automount map as it comes configured by default:
Actual results:
~$ ls /net/snap-
ls: cannot access /net/snap-
Expected results:
~$ ls /net/snap-
bin etc info man sbin
dist include lib share tmp
Additional info:
I filed a bug against Ubuntu autofs4 back in 2007 and they did fix it there:
https:/
I've recently discovered that this problem still exists in the latest Ubuntu for autofs5 and I filed a bug there as well:
https:/
The bug is in the default auto.net handling script that comes with autofs, so I also sent a bug report upstream to the autofs maintainers at <email address hidden> but unfortunately that mailing list doesn't appear to be archived anywhere anymore so I can't give you a link.
I've attached my patch to fix the problem here as well.