Locking problems in 2.2.2

[David W. Chapman Jr.]

On Mon, Dec 03, 2001 at 02:30:25PM -0800, Jeremy Allison wrote:
> Well all the message is telling you is that Samba sent
> an oplock break message to the client and the client
> didn't respond. Samba doesn't know why. Problems could
> be in any of the hardware/software components between.
> 
> > Since this is a production machine, I'm not able to toy with it too much.
> > I'll see what I can do, of course.
> 
I've also been seeing something similiar with 2.2.2 on FreeBSD 
4.4-STABLE

[2001/11/30 14:33:53, 0] smbd/oplock.c:oplock_break(786)
  oplock_break: receive_smb timed out after 30 seconds.
  oplock_break failed for file companies/MBMS/vnc/mbms-application.vnc (dev = 20d04, inode = 470688).
[2001/11/30 14:33:53, 0] smbd/oplock.c:oplock_break(859)
  oplock_break: client failure in oplock break in file companies/MBMS/vnc/mbms-application.vnc
[2001/11/30 14:34:03, 0] smbd/oplock.c:oplock_break(779)
  oplock_break: end of file from client
  oplock_break failed for file companies/MBMS/vnc/mbms-application.vnc (dev = 20d04, inode = 470688).
[2001/11/30 14:34:03, 0] smbd/oplock.c:oplock_break(870)
  oplock_break: client failure in break - shutting down this smbd.

Its only on one machine that I can tell, so it might be hardware related, but I haven't seen it until around samba 2.2.1  

-- 
David W. Chapman Jr.
dwcjr at inethouston.net	Raintree Network Services, Inc. <www.inethouston.net>
dwcjr at freebsd.org	FreeBSD Committer <www.FreeBSD.org>