OpLocks and file sizes.

[Christopher R. Hertel]

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.

- If the server runs out of space, or if the file exceeds quota, is it
  true that the client only finds out when the writes are sent to the
  server?

- If another client requests file size information, does that cause an
  OpLock break so that the "real" current size is reported, or does the
  Windows server just return what it knows?

- Are there any other meta-data operations that might cause an OpLock
  break from the server?

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