Messages in this thread | | | Date | Sun, 18 Dec 2005 15:00:52 -0500 | Subject | Re: lockd: couldn't create RPC handle for (host) | From | Ryan Richter <> |
| |
On Sun, Dec 18, 2005 at 02:31:07PM -0500, Trond Myklebust wrote: > On Sun, 2005-12-18 at 13:01 -0500, Ryan Richter wrote: > > Code: 48 39 78 18 75 1c 8b 86 8c 00 00 00 a8 01 74 12 83 c8 02 89 > > RIP <ffffffff801dbd9e>{nlmclnt_mark_reclaim+62} RSP <ffff81007dfade70> > > CR2: 0000000000000018 > > Looks like the global lock list is corrupted. Could you cat the contents > of /proc/locks?
$ cat /proc/locks 1: POSIX ADVISORY WRITE 1657 00:0e:1771273 0 EOF 2: FLOCK ADVISORY WRITE 1486 00:0e:1770759 0 EOF 3: FLOCK ADVISORY WRITE 1478 00:0e:1770399 0 EOF
> > Every machine with a dead lockd has had this oops. Other stuff that > > looks related (these came after the oops, a few days later): > > Those errors are unrelated. These errors come from the server. > > > lockd: unexpected unlock status: 1 > > lockd: weird return 7 for CANCEL call > > Error "7" is the equivalent of "ESTALE" (stale filehandle). That means > either someone deleted the file you are trying to lock on the server, or > that a bug caused nfsd to somehow lose track of the file. > > I suspect the Error "1" is related to the same issue.
Unfortunately I don't have a date stamp for these messages. I think they might be from my initial efforts to debug the problem - I deleted some lock files once or twice. None of the other machines had these messages.
> > > > Finally, please do > > > > > > echo 1 > /proc/sys/sunrpc/rpc_lockd > > > then unmount one of your NFS partitions, and then mount it again. > > > > That file doesn't exist. > > > > $ ls /proc/sys/sunrpc > > nfs_debug nfsd_debug nlm_debug rpc_debug tcp_slot_table_entries > > udp_slot_table_entries > > Sorry, I meant 'nlm_debug'.
OK, I did that and unmounted and remounted the home directories. There's still no lockd process. I had someone using kde log in, and the login hung for a couple of minutes but then proceeded - it didn't do that before. There were no kernel messages.
-ryan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |