Bug 538317 - kernel 2.6.27.29-0.1 breaks NFS4: Incorrect mount option
Summary: kernel 2.6.27.29-0.1 breaks NFS4: Incorrect mount option
Status: RESOLVED DUPLICATE of bug 531633
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 11.1
: P2 - High : Critical (vote)
Target Milestone: ---
Assignee: Neil Brown
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-11 08:16 UTC by Lars Behrens
Modified: 2009-11-13 10:42 UTC (History)
7 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Behrens 2009-09-11 08:16:23 UTC
+++ This bug was initially created as a clone of Bug #531633 +++

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

Though the initial bug is marked as fixed, we can't mount nfs4 here because of the
"mount.nfs4: an incorrect mount option was specified"-bug.

This is quite a bummer, because our working group's clients are heavily making use of nfs 4.

Reproducible: Always

Same steps to reproduce here:

# grep /home/pcs /etc/fstab
XXX.XX.XXX.XX:/pcs      /home/pcs       nfs4    defaults,noatime 0 0
# mount /home/pcs/
mount.nfs4: an incorrect mount option was specified
# uname -a
Linux XXXXX 2.6.27.29-0.1-default #1 SMP 2009-08-15 17:53:59 +0200 x86_64 x86_64 x86_64 GNU/Linux

Copied the initial bug, because that was for i686.
Comment 1 Neil Brown 2009-11-13 02:55:14 UTC
According to the last comment in the bug that you cloned, an update
was released for x86_64, which is the platform you want.

Have you tried applying all current updates?
Comment 2 Lars Behrens 2009-11-13 09:59:38 UTC
As there was no notice, I hadn't tried it up till now. Just checked an it works here with

2.6.27.37-0.1-default #1 SMP 2009-10-15 14:56:58 +0200 x86_64 x86_64 x86_64 GNU/Linux
Comment 3 Neil Brown 2009-11-13 10:42:45 UTC
Great!  I'll close the bug then.

*** This bug has been marked as a duplicate of bug 531633 ***