fcntl F_SETLKW64

[Jeremy Allison]

On Thu, Dec 20, 2001 at 08:12:21PM +0000, Romeril, Alan wrote:

> Messages like this appear in the logs..
> 
> [2001/12/20 18:42:08, 0] smbd/oplock.c:oplock_break(833)
>   oplock_break: client failure in oplock break in file
> pc/hh-ccs1.pds/templates/netscape.htm
> [2001/12/20 18:42:08, 0] smbd/reply.c:reply_lockingX(4384)
>   reply_lockingX: Error : oplock break from client for fnum = 4659 and
> no oplock granted on this file (pc/hh-ccs1.pds/templates/netscape.htm).


This is a warning though, not an error.


This next packet is the oplock break request....

> Server to Client, SMBlockingX Response
> 
> 0000  00 01 02 9d 4f 37 00 01  30 90 a9 00 08 00 45 00   ....O7..
> 0.....E. 
> 0010  00 5f 75 b6 40 00 3d 06  08 a0 81 1f 64 0b 9b c6   ._u. at .=.
> ....d... 
> 0020  3e 52 00 8b 05 0d c2 82  d4 96 cc be f8 51 50 18   >R......
> ....øQP. 
> 0030  fa f0 03 a2 00 00 00 00  00 33 ff 53 4d 42 24 00   ........
> .3.SMB$. 
> 0040  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ........
> ........ 
> 0050  00 00 03 00 ff ff 00 00  ff ff 08 ff 00 00 00 33   ........
> .......3 
> 0060  12 02 01 00 00 00 00 00  00 00 00 00 00            ........
> .....   
> 

> 30 second gap...

And here is the response.

> Client to server, SMBlockingX Request
> 
> 0000  00 01 30 90 a9 00 00 01  02 9d 4f 37 08 00 45 00   ..0.....
> ..O7..E. 
> 0010  00 5f 67 b4 40 00 80 06  d3 a1 9b c6 3e 52 81 1f   ._g. at ...
> ....>R.. 
> 0020  64 0b 05 0d 00 8b cc bf  08 51 c2 83 09 b0 50 18   d.......
> .Q....P. 
> 0030  43 95 29 95 00 00 00 00  00 33 ff 53 4d 42 24 00   C.).....
> .3.SMB$. 
> 0040  00 00 00 18 07 48 00 00  00 00 00 00 00 00 00 00   .....H..
> ........ 
> 0050  00 00 03 00 ff fe 66 00  ff ff 08 ff 00 de de 33   ......f.
> .......3 
> 0060  12 12 01 ff ff ff ff 00  00 00 00 00 00            ........
> .....    
> 
> 
> Why is the break from the client taking so long to arrive?

Don't know. I've always wondered why Windows clients take so long
to do things with oplocks sometimes. Client bugs would be my guess
(sometimes they don't answer them at all).

Did the smbd process waiting for the break to return time out ?
(ie. did you get the "oplock_break: client failure in oplock break"
message ?).

Jeremy.