Locking problems in 2.2.2

[Jeremy Allison]

On Mon, Dec 03, 2001 at 10:35:22PM +0100, Jurjen Oskam wrote:

> It's unlikely that there are physical networking problems (cables,
> hubs or NICs). ifconfig show zero errors, and all other applications
> work perfectly. The exact same machine worked perfectly in its
> previous life as an NT4 server.
> 
> That of course doesn't necessarily mean that the problem is with Samba. It
> could be the Linux kernel (2.2.19) or the driver for the NIC
> (3c905c).
> 
> Is it possible with e.g. tcpdump to diagnose this problem? I can
> provide detailed info, I just need to know where to look. :-)

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.

Thanks,

	Jeremy.