| Both sides previous revision Previous revision Next revision | Previous revision |
| abstract:mills:filesystems:filesystems [2018-05-23 10:35] – [Using Mills' filesystems] anita | abstract:mills:filesystems:filesystems [2021-07-15 14:31] (current) – old revision restored (2018-06-08 00:43) anita |
|---|
| </note> | </note> |
| |
| <note warning>Please use the custom [[:abstract:mills:filesystems:filesystems:Lustre-utilities|Lustre utilities]] to remove files on all Lustre filesytems ''/lustre/work'' or ''/lustre/scratch'', or to check disk usage on ''/lustre/scratch''.</note> | <note warning>Please use the custom [[abstract:mills:filesystems:lustre#lustre-utilities|Lustre utilities]] to remove files on all Lustre filesytems ''/lustre/work'' or ''/lustre/scratch'', or to check disk usage on ''/lustre/scratch''.</note> |
| |
| ==== Node scratch ==== | ==== Node scratch ==== |
| **Private work directory**: Use the [[#lustre|Lustre]] work directory (/lustre/work/<<//investing_entity//>>) for files where high performance is required. Keep just the files needed for | **Private work directory**: Use the [[#lustre|Lustre]] work directory (/lustre/work/<<//investing_entity//>>) for files where high performance is required. Keep just the files needed for |
| your job such as your applications, scripts and large data sets used for input or created for output. Remember the disk is not backed up, so be prepared to rebuild the files if necessary. With batch jobs, the queue script is a | your job such as your applications, scripts and large data sets used for input or created for output. Remember the disk is not backed up, so be prepared to rebuild the files if necessary. With batch jobs, the queue script is a |
| record of what you did, but for interactive work, you need to take notes as a record of your work. Use [[#lustre-utilities|Lustre utilities]] from a compute node to check disk usage and remove files no longer needed. | record of what you did, but for interactive work, you need to take notes as a record of your work. Use [[abstract:mills:filesystems:lustre#lustre-utilities|Lustre utilities]] from a compute node to check disk usage and remove files no longer needed. |
| |
| **Private archive directory**: Use the [[#archive|archive]] directory (/archive/<<//investing_entity//>>) to build applications for you or your group to use as well as important data, source or any other files you want backed-up. This directory and all the make tools are available from the head node. The head node has faster access to /archive than the compute nodes. See | **Private archive directory**: Use the [[#archive|archive]] directory (/archive/<<//investing_entity//>>) to build applications for you or your group to use as well as important data, source or any other files you want backed-up. This directory and all the make tools are available from the head node. The head node has faster access to /archive than the compute nodes. See |
| the [[:general/userguide/05_development|Application development]] section for information on building applications. You should make a "setup" script that your fellow researchers can use to access applications you want to share. A typical workflow is to copy the files needed from /archive to /lustre for the actual run. The /archive system is backed-up with [[#archive-snapshots|snapshots]]. | the [[abstract:mills:app_dev:app_dev|Application development]] section for information on building applications. You should make a "setup" script that your fellow researchers can use to access applications you want to share. A typical workflow is to copy the files needed from /archive to /lustre for the actual run. The /archive system is backed-up with [[#archive-snapshots|snapshots]]. |
| |
| **Public scratch directory**: Use the public [[#lustre|Lustre]] scratch directory (/lustre/scratch or /lustre-scratch) for files where high performance is required. Store files produced as intermediate work files, and remove them when your current project is done. That will free up the public scratch workspace others also need. This is also a good place for sharing files with all users on Mills. Files in this directory are not backed up, and the first subject to removal if the filesystem gets full. Use [[#lustre-utilities|Lustre utilities]] from a compute node to check disk usage and remove files no longer needed. | **Public scratch directory**: Use the public [[#lustre|Lustre]] scratch directory (/lustre/scratch or /lustre-scratch) for files where high performance is required. Store files produced as intermediate work files, and remove them when your current project is done. That will free up the public scratch workspace others also need. This is also a good place for sharing files with all users on Mills. Files in this directory are not backed up, and the first subject to removal if the filesystem gets full. Use [[abstract:mills:filesystems:lustre#lustre-utilities|Lustre utilities]] from a compute node to check disk usage and remove files no longer needed. |
| |
| **Home directory**: Use your [[#home|home]] directory to store small private files. Application software you use will often store its configuration, history and | **Home directory**: Use your [[#home|home]] directory to store small private files. Application software you use will often store its configuration, history and |