rsnt_translations
53,731
edits
Storage and file management: Difference between revisions
Jump to navigation
Jump to search
Marked this version for translation
No edit summary |
(Marked this version for translation) |
||
| Line 33: | Line 33: | ||
* '''SLURM_TMPDIR''': While a job is running, <code>$SLURM_TMPDIR</code> is a unique path to a temporary folder on a local fast filesystem on each compute node reserved for the job. This is the best location to temporarily store large collections of small files (< 1 MB per file). Note: this space is shared between jobs on each node, and the total available space depends on the node specifications. Finally, when the job ends, this folder is deleted. | * '''SLURM_TMPDIR''': While a job is running, <code>$SLURM_TMPDIR</code> is a unique path to a temporary folder on a local fast filesystem on each compute node reserved for the job. This is the best location to temporarily store large collections of small files (< 1 MB per file). Note: this space is shared between jobs on each node, and the total available space depends on the node specifications. Finally, when the job ends, this folder is deleted. | ||
==Breakdown of storage usage per user== | ==Breakdown of storage usage per user== <!--T:23--> | ||
<!--T:24--> | |||
While the command '''diskusage_report''' gives the space and inode usage per user on ''home'' and ''scratch'', it shows the total usage of the group on project. Since the files that belong to a given user could be all over the place under project, it is difficult to get a break down per user and per given project in case a user has access to more than one project. However, a user can get an estimation of his space and inode usage on the entire project file system by running the command: | While the command '''diskusage_report''' gives the space and inode usage per user on ''home'' and ''scratch'', it shows the total usage of the group on project. Since the files that belong to a given user could be all over the place under project, it is difficult to get a break down per user and per given project in case a user has access to more than one project. However, a user can get an estimation of his space and inode usage on the entire project file system by running the command: | ||
<!--T:25--> | |||
<code>lfs quota -u $USER /project</code> | <code>lfs quota -u $USER /project</code> | ||