Subject: Re: nfs locking panic
To: Bill Sommerfeld <firstname.lastname@example.org>
From: Hauke Fath <hauke@Espresso.Rhein-Neckar.DE>
Date: 11/20/1999 18:19:27
At 3:02 Uhr -0000 20.11.1999, Bill Sommerfeld wrote:
>> [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).
>It's supposed to print out info about locked vnodes to the console.
>this looks suspiciously like something other than a vnode lock is
>being left locked..
If you mean the "-266950656" -- I have just learned from Bill Studenmund
that printlockedvnodes() returns void; no use to print a return value like
I did. I.e., the "-266950656" is _not_ the output of the function.
I commented out the panic(), btw., and the message comes up exactly once
during the boot of the client; no problems afterwards, afaics.
"It's never straight up and down" (DEVO)