On Mon, 12 Dec 2016 20:44:08 +0000, Jeff McCashland wrote: > After: > § The object store SHOULD<WBN1> check for byte range lock conflicts on > Open.Stream using the algorithm described in section 2.1.4.10 with ByteOffset > set to InputBuffer.TargetFileOffset, Length set to InputBuffer.ByteCount, > IsExclusive set to TRUE, LockIntent set to FALSE, and Open set to Open. If a > conflict is detected, the operation MUST be failed with > STATUS_FILE_LOCK_CONFLICT. > > § The object store SHOULD<WBN2> check for byte range lock conflicts on Source > using the algorithm described in section 2.1.4.10 with ByteOffset set to > InputBuffer.SourceFileOffset, Length set to InputBuffer.ByteCount, > IsExclusive set to FALSE, LockIntent set to FALSE, and Open set to > InputBuffer.FileHandle. If a conflict is detected, the operation MUST be > failed with STATUS_FILE_LOCK_CONFLICT. > > WBN1: The ReFS file system in Windows Server 2016 does not check for byte > range lock conflicts on Open.Stream. > WBN2: The ReFS file system in Windows Server 2016 does not check for byte > range lock conflicts on Source.
Thanks a lot for the clarification, Jeff. Please feel free to close this ticket. Cheers, David _______________________________________________ cifs-protocol mailing list [email protected] https://lists.samba.org/mailman/listinfo/cifs-protocol
