cc_staff
782
edits
Using nearline storage: Difference between revisions
Jump to navigation
Jump to search
More details about diskusage_report --nearline
(Marked this version for translation) |
(More details about diskusage_report --nearline) |
||
| Line 81: | Line 81: | ||
<!--T:54--> | <!--T:54--> | ||
While [[Transferring_data|transferring data]] with [[Globus]] or any other tool, the data that was on tape gets automatically restored on disk upon reading it. Since tape access is relatively slow, each file restoration can hang the transfer for a few seconds to a few minutes. Therefore, users should expect longer transfer times from Nearline. | |||
For an overview of the state of all files saved on Nearline, '''some clusters''' support the following command: | |||
{{Command|diskusage_report --nearline --per_user --all_users}} | |||
The different <code>Location</code>'s are: | |||
* <code>On disk and tape</code>: this data is available on disk. | |||
* <code>Modified, will be archived again</code>: the newest version of the data is on disk. | |||
* <code>Archiving in progress</code>: the data is being copied or moved to tape. | |||
* <code>On tape</code>: the data is only on tape. | |||
<!--T:24--> | <!--T:24--> | ||
Then, you can determine whether or not a given file has been moved to tape or is still on disk using the <tt>lfs hsm_state</tt> command. "hsm" stands for "hierarchical storage manager". | |||
<!--T:47--> | <!--T:47--> | ||
| Line 110: | Line 119: | ||
<!--T:27--> | <!--T:27--> | ||
You can explicitly force a file to be recalled from tape without actually reading it with the command <code>lfs hsm_restore <FILE></code>. | You can explicitly force a file to be recalled from tape without actually reading it with the command <code>lfs hsm_restore <FILE></code>. | ||
== Cluster-specific information == <!--T:6--> | == Cluster-specific information == <!--T:6--> | ||