Using nearline storage: Difference between revisions

Jump to navigation Jump to search
Marked this version for translation
(Marked this version for translation)
Line 16: Line 16:
*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 ==
== Using Nearline == <!--T:22-->
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.  You may also remove files from nearline.  It's important to realize that Nearline files can be in sevearl different states:
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.  You may also remove files from nearline.  It's important to realize that Nearline files can be in sevearl different states:
* immediately upon creation, the file is on disk, not tape.  this is mainly to avoid having to guess about when you're done putting the file into place.
* immediately upon creation, the file is on disk, not tape.  this is mainly to avoid having to guess about when you're done putting the file into place.
Line 23: Line 23:
* when such a file is recalled, it returns to the second state.
* when such a file is recalled, it returns to the second state.


<!--T:23-->
Thus, you may wish to inquire about the status of a Nearline file:
Thus, you may wish to inquire about the status of a Nearline file:
  lfs hsm_state ~/nearline/def-mine/user/somefile
  lfs hsm_state ~/nearline/def-mine/user/somefile
rsnt_translations
56,420

edits

Navigation menu