<html><body><p><tt>> From: "Simon Thompson (Research Computing - IT Services)" <br>> <S.J.Thompson@bham.ac.uk></tt><br><tt>> <br>> Second part of the question. If a file is transferred to tape (or <br>> compressed maybe as well), does the file still count against quota, <br>> and how much for? As on hsm tape its no longer copies=2. Same for a <br>> compressed file, does the compressed file count as the original or <br>> compressed size against quota? I.e. Could a user accessing a <br>> compressed file suddenly go over quota by accessing the file?<br>> <br></tt><br><tt>Quotas account for space in the file system. If you migrate a user's file to tape, then that user is credited for the space saved. If a later access recalls the file then the user is again charged for the space. Note that HSM recall is done as "root" which bypasses the quota check -- this allows the file to be recalled even if it pushes the user past his quota limit. </tt><br><br><tt>Compression (which is currently in beta) has the same properties. If you compress a file, then the user is credited with the space saved. When the file is uncompressed the user is again charged. Since uncompression is done by the "user" the quota check is enforced and uncompression can fail. This includes writes to a compressed file. </tt><br><br><br><tt><br>> From: Bryan Banister <bbanister@jumptrading.com><br>> <br>> I also would like to know what the output of the ILM "LIST" policy <br>> reports for KB_ALLOCATED for replicated files. Is it the replicated<br>> amount of data?<br>> </tt><br><tt>KB_ALLOCATED shows the same value that stat shows, So yes it shows the replicated amount of data actually used by the file.</tt><br><br><br><tt>-Wayne</tt><br><BR>
</body></html>