[Bug 828442] New: Can't use autofs if NFS server only offers NFSv4
https://bugzilla.novell.com/show_bug.cgi?id=828442 https://bugzilla.novell.com/show_bug.cgi?id=828442#c0 Summary: Can't use autofs if NFS server only offers NFSv4 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: roland.mainz.bugzilla-suse@nrubsig.org QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111101 SUSE/3.6.24-0.2.1 Firefox/3.6.24 We've tried to access OpenSuSE 12.3's nfs server running in NFSv4-only mode (e.g. NFSv2/NFSv3 protocols are disabled since we have to pass some firewalls (later... not in this test setup which is completely without any firewalls... don't worry :-))) via autofs (several variations, including OpenSuSE 12.2, Solaris 11, Solaris 11.1, Illumos etc.) and all clients can't automount it... ;-( ** Server config (IPv4 address is 192.168.2.105): $ exportfs /nfs4test <world> $ ps -ef | fgrep nfs root 2556 1 0 10:29 ? 00:00:00 /usr/sbin/rpc.mountd --no-nfs-version 2 --no-nfs-version 3 root 2559 2 0 10:29 ? 00:00:00 [nfsd4] root 2560 2 0 10:29 ? 00:00:00 [nfsd4_callbacks] root 2561 2 0 10:29 ? 00:00:00 [nfsd] root 2562 2 0 10:29 ? 00:00:00 [nfsd] root 2563 2 0 10:29 ? 00:00:00 [nfsd] root 2564 2 0 10:29 ? 00:00:00 [nfsd] ** Client config (Solaris 11 in this case, IPv4 address is 192.168.2.81, hostname="indianab134x86"): - Server machine is pingable and otherwise reachable without problems (e.g. ssh, X11 etc. all work between server and clients in both directions) - "snoop" (Solaris network traffic analyser) shows the following traffic during an attempt to do $ cd /net/192.168.2.105/ #: -- snip -- $ snoop 192.168.2.105 Using device e1000g0 (promiscuous mode) 192.168.2.105 -> 224.0.0.251 IGMP v2 membership report indianab134x86 -> 192.168.2.105 TCP D=2049 S=47294 Syn Seq=246940684 Len=0 Win=64240 Options=<mss 1460,nop,nop,tstamp 98806 0,nop,wscale 1,nop,nop,sackOK> 192.168.2.105 -> indianab134x86 TCP D=47294 S=2049 Syn Ack=246940685 Seq=2501028985 Len=0 Win=14480 Options=<mss 1460,sackOK,tstamp 1654279 98806,nop,wscale 7> indianab134x86 -> 192.168.2.105 TCP D=2049 S=47294 Ack=2501028986 Seq=246940685 Len=0 Win=64436 Options=<nop,nop,tstamp 98806 1654279> indianab134x86 -> 192.168.2.105 NFS C NULL4 192.168.2.105 -> indianab134x86 TCP D=47294 S=2049 Ack=246940729 Seq=2501028986 Len=0 Win=114 Options=<nop,nop,tstamp 1654280 98806> 192.168.2.105 -> indianab134x86 NFS R NULL4 indianab134x86 -> 192.168.2.105 TCP D=2049 S=47294 Ack=2501029014 Seq=246940729 Len=0 Win=64436 Options=<nop,nop,tstamp 98806 1654280> indianab134x86 -> 192.168.2.105 TCP D=2049 S=47294 Fin Ack=2501029014 Seq=246940729 Len=0 Win=64436 Options=<nop,nop,tstamp 98806 1654280> 192.168.2.105 -> indianab134x86 TCP D=47294 S=2049 Fin Ack=246940730 Seq=2501029014 Len=0 Win=114 Options=<nop,nop,tstamp 1654281 98806> indianab134x86 -> 192.168.2.105 TCP D=2049 S=47294 Ack=2501029015 Seq=246940730 Len=0 Win=64436 Options=<nop,nop,tstamp 98806 1654281> indianab134x86 -> 192.168.2.105 PORTMAP C GETPORT prog=100005 (MOUNT) vers=1 proto=TCP 192.168.2.105 -> indianab134x86 PORTMAP R GETPORT port=0 indianab134x86 -> 192.168.2.105 PORTMAP C GETPORT prog=100005 (MOUNT) vers=1 proto=UDP 192.168.2.105 -> indianab134x86 PORTMAP R GETPORT port=0 -- snip -- Uhm... I'm stuck at this point. The same thing works OK between a Solaris 11 server (running in NFSv4-only mode) and any kind of NFSv4 client. Reproducible: Always Steps to Reproduce: 1. See above Actual Results: Can't use automounter to access test share. Expected Results: Can use automounter to access test share, e.g. $ cd /net/192.168.2.105/ # ... Goal is to get the automounter functional for all operating systems required by the project (e.g. SuSE Linux and Solaris 10/11+Illumos). Severity: Set to "major" since we can't move forward (unless we pick an all-Solaris config if we can't get the Linux trouble fixed). -- 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=828442 https://bugzilla.novell.com/show_bug.cgi?id=828442#c1 Roland Mainz <roland.mainz.bugzilla-suse@nrubsig.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roland.mainz.bugzilla-suse@ | |nrubsig.org --- Comment #1 from Roland Mainz <roland.mainz.bugzilla-suse@nrubsig.org> 2013-07-08 09:19:47 UTC --- More data (from Solaris 11: If I execute a... -- snip -- $ /usr/sbin/showmount -e 192.168.2.105 showmount: 192.168.2.105: RPC: Program not registered -- snip -- .. the "snoop" utility will sample this network traffic: -- snip -- root@indianab134x86:~# snoop 192.168.2.105 Using device e1000g0 (promiscuous mode) indianab134x86 -> 192.168.2.105 PORTMAP C GETPORT prog=100005 (MOUNT) vers=1 proto=TCP 192.168.2.105 -> indianab134x86 PORTMAP R GETPORT port=0 indianab134x86 -> 192.168.2.105 PORTMAP C GETPORT prog=100005 (MOUNT) vers=1 proto=UDP 192.168.2.105 -> indianab134x86 PORTMAP R GETPORT port=0 -- snip -- .. this sounds a lot that the automounter functionality may only work if the portmapper works on the Linux server side... or not ? -- 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=828442 https://bugzilla.novell.com/show_bug.cgi?id=828442#c2 --- Comment #2 from Roland Mainz <roland.mainz.bugzilla-suse@nrubsig.org> 2013-07-08 10:20:04 UTC --- The following seems to fix the issue for SuSE 12.3 _clients: -- snip -- $ cat /etc/auto.nfsv4 * -fstype=nfs4,hard,intr,nodev,nosuid,nosymlink &:/ $ egrep '^/net' /etc/auto.master /net /etc/auto.nfsv4 -- snip -- .. trouble is... this _workaround_ doesn't work for Solaris&&Illumos... ;-( -- 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=828442 https://bugzilla.novell.com/show_bug.cgi?id=828442#c3 --- Comment #3 from Roland Mainz <roland.mainz.bugzilla-suse@nrubsig.org> 2013-07-08 12:23:49 UTC --- The following _workaround_ works for Solaris/Illumos... but at the expense of NFSv3 and browsing (e.g. list available NFS hosts) compatibility: -- snip -- root@indianab134x86:~# fgrep /net /etc/auto_master #/net -hosts -nosuid,vers=4 /net auto_nfsv4 root@indianab134x86:~# cat /etc/auto_nfsv4 * -nosuid,vers=4 &:/ -- snip -- AFAIK the issue is on the Linux since Solaris machines work with the default /net even if both server and client server are forced to be NFSv4-only. -- 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=828442 https://bugzilla.novell.com/show_bug.cgi?id=828442#c Ye Yuan <yyuan@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yyuan@suse.com AssignedTo|bnc-team-screening@forge.pr |nfbrown@suse.com |ovo.novell.com | -- 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=828442 https://bugzilla.novell.com/show_bug.cgi?id=828442#c4 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |roland.mainz.bugzilla-suse@ | |nrubsig.org --- Comment #4 from Neil Brown <nfbrown@suse.com> 2013-07-18 06:46:51 UTC --- (Sorry for delay in getting to this). the MOUNTD protocol is not part of NFSv4, so it is correct for the mountd service to be disabled if only NFSv4 is requested. However it seems that this might be causing your problem. I wouldn't be surprised if solaris enabled mountd even for nfsv4-only. You could test this by editing /etc/init.d/nfsserver and commenting out the line: VERSION_PARAMS="--no-nfs-version 2 --no-nfs-version 3" It don't really follow the examples you gave in comments 2 and 3. You mention "at the expense of NFSv3", but as you don't want to use NFSv3 I fail to see how that is relevant. Maybe just try the above change and if it still doesn't do what you want, a summary of what works and what doesn't would be helpful. -- 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=828442 https://bugzilla.novell.com/show_bug.cgi?id=828442#c5 --- Comment #5 from Neil Brown <nfbrown@suse.com> 2013-10-21 02:05:45 UTC --- Hi, did you have a chance to try the above test? -- 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=828442 https://bugzilla.novell.com/show_bug.cgi?id=828442#c6 --- Comment #6 from Neil Brown <nfbrown@suse.com> 2013-11-11 06:28:46 UTC --- Ping? Can you try the test in comment #4 and report back please. -- 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=828442 https://bugzilla.novell.com/show_bug.cgi?id=828442#c7 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|roland.mainz.bugzilla-suse@ | |nrubsig.org | Resolution| |NORESPONSE --- Comment #7 from Neil Brown <nfbrown@suse.com> 2014-01-20 23:35:02 UTC --- Resolving is NORESPONSE. Please re-open if you can provide test results as described in comment #4. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com