OpLocks and file sizes.

[Christopher R. Hertel]

On 03/26/2012 09:21 PM, Richard Sharpe wrote:
> On Mon, 26 Mar 2012, Christopher R. Hertel wrote:
> 
>> Some quick OpLock questions...
>>
>> Say we've got a file with an exclusive OpLock, and the client is appending
>> to the end of the file (making it a bigger file, of course).  In that case,
>> the server won't know the new size of the file until the writes have been
>> flushed to the server, which would happen on close or OpLock break.
> 
> My experience is that Windows does a one-byte write to extend the actual
> size of the file to the end of each write that would extend the file, even
> though the data goes into the local cache.
> 
> This has the advantage that ENOSPC can be reported sooner than file close time.

That's what I thought might happen, but I don't recall it being there in
[MS-CIFS].

Anyone else have any clues on this?

Thanks!

Chris -)-----

-- 
"Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/     -)-----   crh at ubiqx.mn.org
OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh at ubiqx.org