Skip to content

updated scratch deletion policy #771

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

MoayadS0
Copy link

@MoayadS0 MoayadS0 commented Aug 6, 2024

Missing Scratch Deletion Policy from User Scratch Section

note

I recently worked on updating the User Scratch section on the website. To inform users about data retention, I added a note indicating that data may be deleted after 30 days. I hope this update helps in building greater trust with users.

Copy link
Contributor

@wwarriner wwarriner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @MoayadS0

Welcome! Thank you for the contribution and for helping make this policy clearer. I just have one change to be made, if you could do that I'll merge this.

@@ -184,6 +184,9 @@ Network scratch is available on the login node and each compute node. This stora
!!! warning

Research Computing expects each user to keep their scratch areas clean. **The cluster scratch areas are not to be used for archiving data.** In order to keep scratch clear and usable for everyone, files older than 30 days will be automatically deleted.

**note**: Data held in user scratch may be retained on the system for 30 days. After 30 days, we may delete data to free space. **The user scratch pool is a shared resource**, so please treat it as temporary storage.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please capitalize the "n" in "note".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants