Bugzilla – Bug 531633
kernel 2.6.27.29 (update-test) breaks NFS4: Incorrect mount option
Last modified: 2009-11-13 10:42:46 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux i686; cs-CZ; rv:1.9.0.13) Gecko/2009080200 SUSE/3.0.13-0.1.2 Firefox/3.0.13 After updating the oS 11.1 kernel today to 2.6.27.29 from the testing update repository, I could not mount a NFS4 share. Reverting to 2.6.27.25 has helped. Reproducible: Always Steps to Reproduce: /etc/fstab: nfs.example.org:/home /home nfs4 sec=krb5i,hard,intr 0 0 mount -a Actual Results: mount reported (quoting from memory) "Incorrect mount option" Expected Results: /home mounted It fails the same even without sec=krb5i, so Kerberos is not a problem.
I saw Neil with some nfs4 changes in the log.
Thanks. I managed to reproduce this - my initial test setup was to simplistic to trigger the bug. I need to backport upstream commit dd5cae6e9772ecc62fd374f7a8ec10eb51c96c4d as well. This fixes the problem in my testing. The new patch is committed to the kernel git and I will attach it here for completeness.
Created attachment 313397 [details] Patch as committed.
*** Bug 533724 has been marked as a duplicate of this bug. ***
*** Bug 534616 has been marked as a duplicate of this bug. ***
*** Bug 534328 has been marked as a duplicate of this bug. ***
When will there be a kernel update with this fix? I really need to access my nfs shares on my home server! Please provide a kernel update as soon as possible. Thank you very much! (I'm a little bit disappointed about opensuse quality assurance that a security update breaks such a basic important thing like mounting network shares. Until now I always automatically installed all proposed security updates. Perhaps I shouldn't install kernel updates any more - never touch a running system...)
(In reply to comment #7) > When will there be a kernel update with this fix? I'm afraid I don't know. I'll report here when I find out. In the mean time you can get a recent kernel package from http://ftp.suse.com/pub/projects/kernel/kotd/
NFS4 not working for more than 2 months now, but a fix was there some hours after the bug was opened. Who decides when a fix is delivered to official update servers? It is disappointing, when one opens a bug and does not get a real solution for months. I know some people that won't submit any bugs because they think it's useless. I know that many people work for free for opensuse and i appreciate that, but isn't that frustrating for them too?
We have just released a SLE11/openSUSE 11.1 kernel update fixing/mentioning this bugreport, which has the version 2.6.27.37-0.1.1. unfortunately our QA turnaround times are high, sorry.
Update released for: cluster-network-kmp-default, cluster-network-kmp-xen, ext4dev-kmp-default, ext4dev-kmp-xen, kernel-default, kernel-default-base, kernel-default-debuginfo, kernel-default-debugsource, kernel-default-extra, kernel-ec2, kernel-ec2-base, kernel-ec2-debuginfo, kernel-ec2-debugsource, kernel-ec2-extra, kernel-source, kernel-source-debuginfo, kernel-syms, kernel-xen, kernel-xen-base, kernel-xen-debuginfo, kernel-xen-debugsource, kernel-xen-extra Products: SLE-DEBUGINFO 11 (x86_64) SLE-DESKTOP 11 (x86_64) SLE-HAE 11 (x86_64) SLE-SDK 11 (x86_64) SLE-SERVER 11 (x86_64) SLE-SERVER 11-EC2 (x86_64)
*** Bug 538317 has been marked as a duplicate of this bug. ***