...
| Column |
|---|
|
| Code Block |
|---|
| language | bash |
|---|
| theme | DJango |
|---|
| title | Terminal 1. Check usage of the /scratch quota |
|---|
| $ lfs quota /scratch
Disk quotas for user aelwell (uid 20701):
Filesystem kbytes quota limit grace files quota limit grace
/scratch 1460 0 0 - 14 0 0 - |
|
Best practices
| Column |
|---|
|
| Tip |
|---|
- Data should be moved out of the
/scratch filesystem
|
|
...
| Tip |
|---|
- The
/scratch filesystem is a shared resource that suffers low performance when the number of files increases too much. Users should actively remove their files if no longer in use, rather than waiting for the system to delete them. For this, check Deleting Large Numbers of Files on Lustre Filesystems.
|
| Tip |
|---|
- By default,
/scratch use PFL to stripe files to make best use of the SSD and HDD. This default settings has been set to work for almost all workflows and we recommend not setting the stripping explicitly. For this, check Progressive File Layout (PFL) and File Striping.
|
| Warning |
|---|
- Users should never use the
touch command to avoid purging of their files. The use of the touch command to avoid purging generates overloading of the metadata servers of the /scratch filesystem. Remember that /scratch is shared among all users. Therefore, users should respect the best practices to avoid overloading of metadata servers at all times. Overloading of the metadata servers dramatically degrade performance affecting all users at the same time. Pawsey reserves the right to revoke access to users that do not respect this best practice.
|
|
Purge policy of 30 days
Files on the /scratch filesystem are deleted automatically after 30 days from their last access (reading or modifying). This action is referred to as purging. It is part of a dynamic allocation system Pawsey implements to maximise the availability of space for large-scale, data-intensive computations.
...
Related pages
...