cc_staff
176
edits
Using nearline storage: Difference between revisions
preliminary mention of hsm tools
No edit summary |
(preliminary mention of hsm tools) |
||
| Line 15: | Line 15: | ||
*Files smaller than ~200MB should be combined into archive files (''tarballs'') using [[Archiving and compressing files|tar]] or a similar tool. | *Files smaller than ~200MB should be combined into archive files (''tarballs'') using [[Archiving and compressing files|tar]] or a similar tool. | ||
*Files larger than 300GB should be split in chunks of 100GB using the [[Archiving_and_compressing_files#Other_Useful_Utilities|split]] command or a similar tool. | *Files larger than 300GB should be split in chunks of 100GB using the [[Archiving_and_compressing_files#Other_Useful_Utilities|split]] command or a similar tool. | ||
== Using Nearline == | |||
The basic model for using nearline is that you put files there, and later you may access them. Like a normal filesystem, except that reading the files may involve a significant pause while the content is read from tape. You may also remove files from nearline. One extra operation you may wish to perform is to inquire about the tape status of a file: | |||
lfs hsm_state ~/nearline/def-mine/user/somefile | |||
will report on the HSM status of the file. Normally, to retrieve the file, you can just use it (open, read/write). If you wish to ensure that the file is brought in from tape, you can also: | |||
lfs hsm_restore | |||
== Access == <!--T:6--> | == Access == <!--T:6--> | ||