Messages in this thread | | | From | (Miquel van Smoorenburg) | Subject | Re: PossibleNFS locking problem 2.2.0pre1-4 | Date | 6 Jan 1999 10:12:28 +0100 |
| |
In article <cistron.19990105150301.A1026@parus.itea.ntnu.no>, Jon K. Hellan <Jon.K.Hellan@item.ntnu.no> wrote: >I recently upgraded to 2.2.0-pre4, and apparently have a problem nfs >locking files on an nfs server running 2.0.36 (pre 14, actually). >I am not sure whether this is a kernel bug or a configuration problem.
With a 2.2.0 kernel, the NFS client expects that the server is running a "lockd" process. If it isn't you need to mount the NFS filesystems on the client with the "nolock" option and it will behave just like 2.0
Mike. -- Indifference will certainly be the downfall of mankind, but who cares?
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |