Many applications will attempt to set the EOF to some maximum value
before writing to the file in order to ensure they will have enough room
to complete the entire operation (save, save as, copy, whatever) before
starting. Are you checking for EOF SetFileInfo requests that will extend
beyond quota (and failing them, perhaps with STATUS_DISK_FULL)? You
still have to fail cached writes that extend EOF but applications should
be set up to handle this. If you succeed an EOF extend and then fail
writes that lie beneath that EOF, then that’s where you will have
trouble.
- Nicholas Ryan
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@wrq.com
Sent: Friday, December 20, 2002 11:08 AM
To: File Systems Developers
Subject: [ntfsd] Quotas and cached writes…Hi all - I am adding quota support to our network redirector
(i.e. respecting quotas set on the remote system and failing
create/write actions if they will exceed quota). I am having
trouble correctly handling cached writes that exceed quota.
Here is a concrete example:Open an existing file in MS Word, add enough data to exceed
quota, attempt to save the file. The result is a “disk full”
message (fine), then “lost delayed write” messages and file
corruption (not so fine).In the cached write situation, by the time I have figured out
that I will exceed quota it appears to be to late to do
anything about it. Any ideas or examples of how to correctly
handle this situation would be much appreciated.Thanks,
Kjell**************
Kjell Swedin - Software Engineer - WRQ Inc.WRQ has 21 years of experience providing integration software
and services for host-intensive environments. To learn more
about our Reflection and Verastream products, > visit
<www.wrq.com>
>
> —
> You are currently subscribed to ntfsd as: xxxxx@nryan.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
></www.wrq.com>