Bugzilla – Bug 151024
No file locking possible on nfs mounted dir
Last modified: 2006-03-09 10:29:36 UTC
This looks very much like bug #128784 but I have the latest (YOU) updates of both kernel and nfs* (and everything else) on both sides. I don't see any errors in any logs, just a notice that the server doesn't do TCP and it falls back to udp (no clue why). Both the server and client is Suse 10.0 x86_64 with nfs mounted /home. Any time some application (like gconfd or evolution) tries to take a lock on a file it gets permission denied. Searching for the problem I found a few with similar problem but no resolution (since starting nfslock isn't possible). It seems to be on the server side that the problem is because the same directory mounted from a Mandrake 10.1 server does not have the same problem.
I was running nfs-server-2.2beta51-212.2.x86_64.rpm on the server. After changing to nfs-server-2.2beta51-212.x86_64.rpm it started to work. Given that the server package is a beta I guess this is more of a bug report on the beta51.
Please do not use the old user space nfs server. Uninstall the nfs-server package and install nfs-utils instead. Neil, could you track this please?
As you can see I already done the swap but you could add some info about it. When I installed the server I knew it was going to be a nfs server so I selected the nfs-server package and when I selected nfs-utils it just told me about a conflict so I guessed that nfs-server was a superset of nfs-utils and the package description wasn't that much help in the choice (userspace vs kernel space, I have no clue on what is better or never).
There are a few things I don't understand: 1/ What "swap" have you done? 2/ In comment #1 you say you were running X and after changing to X it started to work. That is the same X. I don't understand. Just to clarify. You DO NOT want nfs-server installed. You DO want nfs-utils installed. Is your main issues that you would like the descriptions of these packages to be clearer, it is there something else?
Sorry, I should have read my own writing I ment to say that I swapped from nfs-server-2.2beta51-212.2.x86_64.rpm to nfs-utils-1.0.7-13.x86_64.rpm so I already done that swap and after that it started to work again. What I'm missing is more doc on one vs the other. You write that I don't want to run nfs-server, why not? if never, why is it even around? I had expected that "rpm -qi" would give some hints on why I should use one over the other, so yes, I want the description to be clearer.
I'm reassigning this to Petr, the maintainer of the SuSE nfs-server package. The suggesting is that the description should be clarified so that people don't install it accidentally. nfs-server is an nfs server that runs in user-space. As such it is a lot slower than the in-kernel nfs server, and does not comply as well the the standards for required behaviour. I believe it is around because it has one or two features that some people want and that are not (and never will be) supported by the in-kernel server. However that is just a guess. (It can do obscure things like following symlinks on the server instead of the client).
I appended following text to nfs-server description: "Userspace NFS server is a lot slower than the kernel NFS server, but has some special features which are not in the kernel NFS server."