Messages in this thread | | | Date | Tue, 08 Sep 1998 13:29:16 -0400 | From | Bill Hawes <> | Subject | Re: NFS lockd problems |
| |
Jamie Lokier wrote: > > I'm having problems with 2.1.119, fcntl file locking and NFS as a client > which I can't explain. > > On trying to read a remote mail spool, mutt tries to lock the mail file > with fcntl (fd, F_SETLK, {F_RDLCK, SEEK_SET, 0, 0}), which returns > -ENOLCK. > > I traced through the kernel source to find how it gets this, and it's > not terribly clear. I got this in the log, with some debugging switched > on. (I'll turn on sunrpc debugging too if it's of interest): > > Sep 7 20:07:43 clpc20 kernel: nsm_mon_unmon: rpc failed, status=-13 > Sep 7 20:07:43 clpc20 kernel: lockd: failed to monitor 163.1.27.1 > > This is output for each attempt to lock the file.
This sometimes means you haven't started statd ...
Regards, Bill
- 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/faq.html
| |