[Bug 855820] New: nfsclients mounts always as nfs4 with security though disabled, leading to 20s boot delay
https://bugzilla.novell.com/show_bug.cgi?id=855820 https://bugzilla.novell.com/show_bug.cgi?id=855820#c0 Summary: nfsclients mounts always as nfs4 with security though disabled, leading to 20s boot delay Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: christian.esken-services@arcor.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 My box is a NFS Client, who mounts several directories from a NFS Server. I am using NFSv3, so I disabled NFSv4 and in the YaST "NFS-Client" module. The Tab "NFS Client configuration" has the settings "Enable NFSv4" and "Enable GSS Security" disabled. Still, all mounts are done using NFSv4, and also it looks like Security is being used. --- Example ---------------------------------------------- # grep Bilder /etc/fstab 1.2.3.4:/volume2/photo /Bilder nfs defaults 0 0 # mount /Bilder # mount | grep Bilder 1.2.3.4:/volume2/photo on /Bilder type nfs4 (rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.2.111,local_lock=none,addr=1.2.3.4) One can see, the mount has "type nfs4" and also "vers=4.0" as options. --- Impact ---------------------------------------------- 1) Bad mount. I really need nfs3 at this point of time. 2) Boot delay of about 20 seconds, apparently while some NFS security is probed. Excerpt from /var/log/warn: --------------------------------------- 2013-12-17T09:45:30.282685+01:00 whitefall ModemManager[649]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:15.1/0000:06:00.0': not supported by any plugin --- 19 seconds nothing is happening --------------- 2013-12-17T09:45:49.895152+01:00 whitefall rpc.gssd[2797]: ERROR: gssd_refresh_krb5_machine_credential: no usable keytab entry found in keytab /etc/krb5.keytab for connection with host nas 2013-12-17T09:45:49.896081+01:00 whitefall rpc.gssd[2797]: ERROR: No credentials found for connection to server nas --------------------------------------- Hint: If I manually change "defaults" with "sec=sys,vers=3.0", then the mount is being done using nfsv3. Reproducible: Always Steps to Reproduce: 1. Add a NFS mount, disable "NFSv4" and "GSS Security" 2. Mount it Actual Results: Mount was done using NFSv4 instead of NFSv3. 20 second boot delay. Expected Results: Mount is done using NFSv3. No boot delay. -- 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=855820 https://bugzilla.novell.com/show_bug.cgi?id=855820#c Christian Esken <christian.esken-services@arcor.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|nfsclients mounts always as |nfsclients mounts always as |nfs4 with security though |nfs4 with security (though |disabled, leading to 20s |disabled), leading to 20s |boot delay |boot delay -- 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=855820 https://bugzilla.novell.com/show_bug.cgi?id=855820#c Xiyuan Liu <xyliu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyliu@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=855820 https://bugzilla.novell.com/show_bug.cgi?id=855820#c1 --- Comment #1 from Neil Brown <nfbrown@suse.com> 2013-12-19 02:47:56 UTC --- The YaST NFSv4 setting is only part of the story. If the server provides NFSv4, the client will use NFSv4 unless you give the mount option "vers=3". A fix for the boot delay has been submitted for the kernel package. I don't know when it will be released. -- 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=855820 https://bugzilla.novell.com/show_bug.cgi?id=855820#c2 --- Comment #2 from Christian Esken <christian.esken-services@arcor.de> 2013-12-19 12:20:23 UTC --- Thanks for your quick response. I can confirm that the Server [1 ]recently was upgraded with NFSv4 support. I have updated first the NFS Server, and shortly after that "upgraded" my NFS ClientOS (from Ubuntu to openSUSE 13.1). The only thing that confuses me now is, why there is a "YaST NFSv4 setting" at all, if finally the NFS server overrides that setting. Or is this a "require NFSv4" setting, and the mount fails if the switch is active for a server only supporting NFSv3 (last line in the following table). In that case the setting should IMO be renamed from "Activate NFSv4" to "Require NFSv4". YaST-Setting Server-Support Resulting mount OFF v4 v4 ON v4 v4 OFF v3 v3 ON v3 v3 or fail(?) --- [1] The server is a Synology NAS, and Synology recenetly added support for NFSv4. -- 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=855820 https://bugzilla.novell.com/show_bug.cgi?id=855820#c3 Neil Brown <nfbrown@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #3 from Neil Brown <nfbrown@suse.com> 2014-01-21 02:22:35 UTC --- The "Enable NFSv4" setting "NFS Settings" in the NFS {Client,Server} Configuration in YAST causes the "rpc.idmapd" daemon to be run, which is needed for NFSv4, but not for v2 or v3. So it really is "enable", not "activate" or "require". Also if it isn't enabled, the NFS server will not export with NFSv4. When you try to mount something it will always use the highest version support by both client and server, unless explicitly requested otherwise. So if you mount from an NFSv4 server without "Enable NFSv4" selected, then it might fail ... though in recent kernels the NFS client doesn't use rpc.idmapd so maybe it will. Yes I appreciate that this is not really ideal. Things keep changing and it is hard to keep up. I hope to substantially revise the NFS startup soon to work properly with systemd. I'll try to make it more seemless when I do that. I'm going to mark this as "FIXED" for now as I think the 30 delay has been address and the other issues are being tracked elsewhere. Thanks. -- 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=855820 https://bugzilla.novell.com/show_bug.cgi?id=855820#c4 --- Comment #4 from Christian Esken <christian.esken-services@arcor.de> 2014-01-26 22:13:51 UTC --- Thanks for the reply. Yes, the delay issue is fixed, as far as I see. So lets keep this ticket closed. -- 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