lkml.org 
[lkml]   [1999]   [Dec]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectNFS locking
From
>>>>> " " == Miklos Szeredi <Miklos.Szeredi@eth.ericsson.se> writes:

> Hi! NFS locking does not seem to work with Linux clients and
> Solaris server. The fcntl locking request returns ENOLCK and in
> the kernel log the following lines are printed:

> Dec 7 15:58:27 bcica kernel: nsm_mon_unmon: rpc failed,
> status=-13 Dec 7 15:58:27 bcica kernel: lockd: failed to
> monitor 164.48.158.2

> Locking does work on Solaris clients, with the same server.

> Should this work or not?

It should work if you're running an 'rpc.statd' daemon. The Linux
kernel does not support so-called 'unmonitored' locking, hence both
the client and the server need to be running a statd process. This
ensures that if the server (client) reboots, then all remote locks are
reclaimed by the client (released by the server).

Cheers,
Trond

-
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/

\
 
 \ /
  Last update: 2005-03-22 13:55    [W:0.064 / U:0.180 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site