Subject: Re: nfs locking panic
To: Hauke Fath <hauke@Espresso.Rhein-Neckar.DE>
From: Bill Studenmund <email@example.com>
Date: 11/18/1999 14:09:04
On Thu, 18 Nov 1999, Hauke Fath wrote:
> A few printf()s later and with a -current kernel, I got
> [hauke@elmo] ~ > ../../../../nfs/nfs_syscalls.c, line 618: p->p_locks = 1,
> ount = 0 !
> Locked vnodes
> printlockedvnodes() says -266950656 ...
> nfsd: locking botch in op 3
> -- printlockedvnodes() may be bogus, I don't know what it returns (I used %d).
Note: printlockedvnodes returns void - it's supposed to walk the mount
lists and show you all the locked vnodes.