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.
tcpdump shows no ethernet traffic while this happens. There is some NFS
traffic at first, but then only a little and only sometimes to refresh
the cache. All the NFS transactions replied ok anyway.
I'm currently mounting with nolock, which is silly on a mail directory I
know but up until yesterday I was using 2.0.35 on that machine anyway,
which I gather is just as silly :-)
Any ideas?
-- Jamie
-
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