Problems with SAMBA 2.2.2 Oplocks

[David Collier-Brown]

Drew.Zeller at statcan.ca wrote:
> [2002/01/10 11:27:06, 0] smbd/oplock.c:(1026)
>   request_oplock_break: no response received to oplock break request to pid
> 29920 on port 52339 for dev = 40050001, inode = 31477  for dev = 40050001,
> inode = 31477, tv_sec = 3c18bba8, tv_usec = e2dca

> [2002/01/10 11:27:06, 0] smbd/open.c:(554)
>   open_mode_check: exlusive oplock left by process 29920 after break ! For
> file windows/extend.dat, dev = 40050001, inode = 31477. Deleting it to
> continue...
> [2002/01/10 11:27:06, 0] lib/util.c:(1055)
>   PANIC: open_mode_check: Existant process 29920 left active oplock.

	I'm discussing this with Drew in email, but
	I find the final message above worrysome...

	My code at work doesn't match this, so can 
	someone double-check and see if we **really**
	are panicking?  That would imply that we're
	killing the victim of the orphaned lock
	rather than the culprit (:-0)

--dave
-- 
David Collier-Brown,           | Always do right. This will gratify 
Performance & Engineering      | some people and astonish the rest.
Americas Customer Engineering, |                      -- Mark Twain
(905) 415-2849                 | davecb at canada.sun.com