[cifs-protocol] [REG:113102210883291] - [MS-SMB2] 220.127.116.11.1 NT_STATUS_REQUEST_NOT_ACCEPTED?
Volker.Lendecke at SerNet.DE
Wed Nov 13 04:05:31 MST 2013
On Wed, Nov 13, 2013 at 03:21:01AM +0000, Edgar Olougouna wrote:
> The last Create is transitioning the oplock state to BREAK_TO_TWO_TO_NONE while the previous oplock BREAK_TO_TWO is still unacknowledged.
> This explains why the ack to Level2 returned the error.
> >From server implementation perspective, you can either explicitly ack straight to None (FSCTL_OPLOCK_BREAK_ACK_NO_2) or ack and end up with either Level2 or None, depending on the state of the oplock when your ack shows up (FSCTL_OPLOCK_BREAK_ACKNOWLEDGE).
> Let's me know whether this helps.
Well, not really. I don't have NTFS available, so I don't
have FSCTLs around. I was searching for the explanation of
the wire-visible behaviour in MS-SMB2 and MS-FSA. Can you
give me pointers where in those documents I can find the
explanation, or point me at other protocol document?
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt at sernet.de
More information about the cifs-protocol