Bug 140766

Summary:	autofs parse_sun.so broken and /net mounts of NFS partitions from Linux not working
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Bill Hill <bill>
Component:	Other	Assignee:	Chris L Mason <mason>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	bill
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Bill Hill 2005-12-22 15:51:19 UTC

I have autofs-4.1.4-6 installed and running under SUSE 10.0 (Eval) on an IBM T23 laptop which mounts exported NFS partitions from Solaris servers correctly, eg on Solaris server have

server# share
/export/system0   rw=hgu_hosts   ""

this is mounted as

/net/server/export/system0

But partitions from Linux workstations are not mounted correctly, eg on Mandrake 10.1 workstation have

wstation# exportfs
/export/data0   <world>

usualy this is not mounted  but from some workstations the contents of /export/data0 appear in /net/wstation not in /net/wstation/export/data0 as expected.

I've seen the same problem with workstations exporting NFS partitions that are running Mandrake 10.1 or SUSE 10.0.

Using the debug option with automount I get output like

parse(sun): mounting root /net, mountpoint wstation, what /export/data0 wstation:/export/data0, fstype nfs, options hard,intr,nodev,nosuid

for the server partition (the mount that works) I get 

parse(sun): mounting root /net/server, mountpoint /export/system0, what server:/export/system0, fstype nfs, options hard,intr,nodev,nosuid

As a workaround copying parse_sun.so from a workstation running Mandrake 10.1 (autofs-4.1.2-1mdk) to /usr/lib/autofs on the SUSE laptop fixes the problem and the mounts all appear correctly.

Comment 1 Andrew Jorgensen 2006-03-24 23:09:06 UTC

I am seeing the same issue on a SuSE 10.0 box.  There was a brief discussion on the autofs mailing list back in August 2005.  It appears that this is a SuSE bug and that it comes and goes from time to time and has something to do with the patches that are included in the SuSE build of the software.  Or perhaps it is an upstream bug and it used to be patched downstream.

http://hera.kernel.org/pipermail/autofs/2005-August/thread.html#2433

The difference for me between hosts that work and hosts that don't is if they have more than one filesystem exported.  I suspect that the original poster has the same situation and didn't notice that this was the difference.

Comment 2 Andrew Jorgensen 2006-03-24 23:18:23 UTC

A coworker pointed out that I made it sound like the bug was intermittent.  It isn't.  I meant that it has existed in some builds / versions of autofs in SuSE ditros and not in others.  I suspect that the patch that fixed it was removed when the package was updated to 4.1.4 and that the fix never made it upstream.

From the changelog:
Mon May 23 00:12:23 CEST 2005 - ro@suse.de
- update to 4.1.4, remove upstream patches

Can the maintainer confirm this bug please?

Comment 3 Greg Kroah-Hartman 2006-08-14 07:12:19 UTC

Closed due to inactivity.