Scratch purging policy: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 6: Line 6:


<!--T:1-->
<!--T:1-->
The scratch filesystem on our clusters is intended as temporary, fast storage for data being used during job execution.  Data needed for long term storage and reference should be kept in either [[Project layout|<code>/project</code>]] or other archival storage areas. In order to ensure adequate space on scratch, files older than 60 days are periodically deleted according to the policy outlined in this page.  Note that the purging of a file is based on its age, not its location within scratch; simply moving a file from one directory in scratch to another directory in scratch will not in general prevent it from being purged.   
The scratch filesystem on our clusters is intended as temporary, fast storage for data being used during job execution.  Data needed for long-term storage and reference should be kept in either [[Project layout|<code>/project</code>]] or other archival storage areas. In order to ensure adequate space on scratch, files older than 60 days are periodically deleted according to the policy outlined in this page.  Note that the purging of a file is based on its age, not its location within scratch; simply moving a file from one directory in scratch to another directory in scratch will not in general prevent it from being purged.   


=Expiration procedure= <!--T:2-->
=Expiration procedure= <!--T:2-->
Line 14: Line 14:


<!--T:4-->
<!--T:4-->
On the 12th of the month, a final notification e-mail will be sent with an updated assessment of candidate files for expiration on the 15th, giving you 72 hours to make arrangements for moving these files. At the end of day on the 15th, any remaining files on the scratch filesystem for which both the <code>ctime</code> and the <code>atime</code> are older than 60 days will be deleted. Please remember that the e-mail reminders and login notice are a courtesy offered to our users, whose ultimate responsibility it is to keep files older than 60 days from being located in the scratch space.  
On the 12th of the month, a final notification e-mail will be sent with an updated assessment of candidate files for expiration on the 15th, giving you 72 hours to make arrangements for moving these files. At the end of the day on the 15th, any remaining files on the scratch filesystem for which both the <code>ctime</code> and the <code>atime</code> are older than 60 days will be deleted. Please remember that the e-mail reminders and login notice are a courtesy offered to our users, whose ultimate responsibility it is to keep files older than 60 days from being located in the scratch space.  


<!--T:5-->
<!--T:5-->
Line 22: Line 22:


<!--T:14-->
<!--T:14-->
* On cedar, beluga and graham clusters go to the '''/scratch/to_delete/''' path  and look for a file with your name.  
* On Cedar, Beluga and Graham clusters go to the '''/scratch/to_delete/''' path  and look for a file with your name.  
* On niagara go to '''/scratch/t/to_delete/''' (symlink to /scratch/t/todelete/current)
* On Niagara go to '''/scratch/t/to_delete/''' (symlink to /scratch/t/todelete/current)
</pre>
</pre>
The file will contain a list of filenames with full path, possibly other information about atime, ctime, size, etc. It will be updated only on the 1st and the 12th of each month. If a file with your name is there it means you have candidates slated for purging, otherwise there is nothing to worry about that month.  
The file will contain a list of filenames with full path, possibly other information about atime, ctime, size, etc. It will be updated only on the 1st and the 12th of each month. If a file with your name is there, it means you have candidates slated for purging, otherwise there is nothing to worry about that month.  


<!--T:15-->
<!--T:15-->
rsnt_translations
56,430

edits

Navigation menu