Bureaucrats, cc_docs_admin, cc_staff
2,306
edits
Using nearline storage: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 26: | Line 26: | ||
The "hsm" used in this command stands for "hierarchical storage manager". When you attempt to read a file which is on tape, the system will automatically copy it back from tape to disk; this may take a few minutes or even a few hours if the tape system is very busy. If you wish to explicitly force a file to be recalled from tape, you can use the <code>lfs hsm_restore <FILE></code> command. | The "hsm" used in this command stands for "hierarchical storage manager". When you attempt to read a file which is on tape, the system will automatically copy it back from tape to disk; this may take a few minutes or even a few hours if the tape system is very busy. If you wish to explicitly force a file to be recalled from tape, you can use the <code>lfs hsm_restore <FILE></code> command. | ||
Note that the output of the command <code>diskusage_report</code> does not provide reliable statistics on the consumption of nearline on the clusters [Graham] and [Béluga/en]. | |||
== Using nearline == <!--T:3--> | == Using nearline == <!--T:3--> | ||
Because of the delay in reading from tape, nearline is not intended to be used by jobs where allocated time would be wasted. It is only accessible as a directory on certain nodes of the clusters, but never on compute nodes. | Because of the delay in reading from tape, nearline is not intended to be used by jobs where allocated time would be wasted. It is only accessible as a directory on certain nodes of the clusters, but never on compute nodes. | ||