Using nearline storage: Difference between revisions

Jump to navigation Jump to search
Marked this version for translation
No edit summary
(Marked this version for translation)
Line 9: Line 9:
This is useful because the capacity of our tape libraries is both large and expandable.  When a file has been moved to tape (or ''virtualized''), it still appears in the directory listing.  If the virtual file is read, the reading process will block for some time, probably a few minutes, while the file contents is copied from tape to disk.
This is useful because the capacity of our tape libraries is both large and expandable.  When a file has been moved to tape (or ''virtualized''), it still appears in the directory listing.  If the virtual file is read, the reading process will block for some time, probably a few minutes, while the file contents is copied from tape to disk.


<!--T:24-->
You can tell that a file is on tape or still on disk with the <code>lfs hsm_state</code> command:
You can tell that a file is on tape or still on disk with the <code>lfs hsm_state</code> command:


<!--T:25-->
<source lang="bash">
<source lang="bash">
# Here, <FILE> is still on the disk
# Here, <FILE> is still on the disk
Line 16: Line 18:
<FILE>: [...]: exists archived, [...]
<FILE>: [...]: exists archived, [...]


<!--T:26-->
# Here, <FILE> is archived on tape, there will be a lag when opening it.  
# Here, <FILE> is archived on tape, there will be a lag when opening it.  
$ lfs hsm_state <FILE>
$ lfs hsm_state <FILE>
Line 21: Line 24:
</source>
</source>


<!--T:27-->
"HSM" stands for "hierarchical storage manager". If you wish to ensure that the file is brought in from tape, you can use
"HSM" stands for "hierarchical storage manager". If you wish to ensure that the file is brought in from tape, you can use
  lfs hsm_restore <FILE>
  lfs hsm_restore <FILE>
rsnt_translations
56,420

edits

Navigation menu