Handling quota and out of space issues while holding an OpLock

[Richard Sharpe]

Hi,

I have noticed that windows clients tend to send requests to extend the
file size even though they are holding an oplock on a file.

It struck me that this must be so they can deal with issues like out of
quota or out of space at the point at which they occur, and thus give the
application a useful error message, rather than trying to deal with these
things at file close time (ie, trying to flush lots of data to the file
server could result in an EXQUOTA or NOSPACE return, and thus the close
operation must fail, however, the application might not even bother to
check the result of the close operation, and by that stage, there is no
way to recover etc).

Has anyone else observed this? Can anyone comment?

Regards
-----
Richard Sharpe, rsharpe[at]richardsharpe.com, rsharpe[at]samba.org,
sharpe[at]ethereal.com, http://www.richardsharpe.com