[Bug 718881] New: autofs does not mount specific folders
https://bugzilla.novell.com/show_bug.cgi?id=718881 https://bugzilla.novell.com/show_bug.cgi?id=718881#c0 Summary: autofs does not mount specific folders Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: munderl@tnt.uni-hannover.de QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; de) Presto/2.9.168 Version/11.51 Since upgrading to tumbleweed, we have problems with autofs. The source seems to be the autofs4 kernel module, not the automounter daemon. Problem is, our zypper repos are on an autofs folder, e.g. /data/suse/updates/tumbleweed. If zypper tries to access this folder, it fails (zypper: Specified path '/data/suse/updates/tumbleweed/' is not a directory: dir:///data/suse/updates/tumbleweed/). ls -l /data/suse also fails (cannot access suse: No such file or directory). However, ls /data/suse (without -l) works, as does ls -l /data/suse/ (/ at the end). If /data/suse ist mounted, zypper works fine. If the automounter daemon is started in forground mode (-f), it does not give any output when mounting fails, so I assume it its not called by the autofs module at all? Reproducible: Always Steps to Reproduce: 1. See description above 2. 3. Actual Results: ls: cannot access suse: No such file or directory zypper: Specified path '/data/suse/updates/tumbleweed/' is not a directory: dir:///data/suse/updates/tumbleweed/ Expected Results: auto mount directory -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=718881
https://bugzilla.novell.com/show_bug.cgi?id=718881#c1
--- Comment #1 from Marco Munderloh
200) instead of just displaying the paths and not mounting them (as it was before). This seems to be a different bug and is already reported as bug
https://bugzilla.novell.com/show_bug.cgi?id=718881
https://bugzilla.novell.com/show_bug.cgi?id=718881#c2
Marco Munderloh
https://bugzilla.novell.com/show_bug.cgi?id=718881
https://bugzilla.novell.com/show_bug.cgi?id=718881#c3
--- Comment #3 from Marco Munderloh
https://bugzilla.novell.com/show_bug.cgi?id=718881
https://bugzilla.novell.com/show_bug.cgi?id=718881#c4
--- Comment #4 from Marco Munderloh
https://bugzilla.novell.com/show_bug.cgi?id=718881
https://bugzilla.novell.com/show_bug.cgi?id=718881#c
Leonardo Chiquitto
https://bugzilla.novell.com/show_bug.cgi?id=718881
https://bugzilla.novell.com/show_bug.cgi?id=718881#c5
Leonardo Chiquitto
https://bugzilla.novell.com/show_bug.cgi?id=718881
https://bugzilla.novell.com/show_bug.cgi?id=718881#c6
Marco Munderloh
https://bugzilla.novell.com/show_bug.cgi?id=718881
https://bugzilla.novell.com/show_bug.cgi?id=718881#c7
Leonardo Chiquitto
participants (1)
-
bugzilla_noreply@novell.com