Bug 133619 - NFSv3 Locking is broken in server code
Summary: NFSv3 Locking is broken in server code
Status: RESOLVED DUPLICATE of bug 128784
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: i686 Other
: P5 - None : Critical
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-13 23:18 UTC by Sebastian Hasait
Modified: 2005-11-14 12:05 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Hasait 2005-11-13 23:18:28 UTC 
I use NFSv3 for /home. All users with homedir in /home cannot start Eclipse - it complains about Stale NFS file handle in its locking code, although basic NFS works fine. For users with local(non-NFS) homedir can start Eclipse.
Replacing at the NFS-Server SuSE10 with FedoraCore4 solves the problem, but i want to use SuSE10 and not FC4.
I recompiled the SuSE-kernel without NFSv4 support but the locking problem stays. In the logfiles nothing strange about lockd or nfsd.
Something must be different between FedoraCore4 and SuSE10, so it works for FC4 but not for SuSE10.
Please make it run, i have no ideas - additional info can be provided on request - Thanx - continue your great work!!
Comment 1 Olaf Kirch 2005-11-14 12:05:23 UTC 
This is a known bug - please try the latest kernel from 
ftp://ftp.suse.com/pub/projects/kernel/kotd, this should fix the
problem. 

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