Using nearline storage: Difference between revisions

Using nearline storage (view source)

48 bytes removed , 6 years ago

Bureaucrats, cc_docs_admin, cc_staff

2,879

edits

@@ Line 2: / Line 2: @@
 ==Nearline is a filesystem virtualized onto tape==
-Nearline storage is like [[Project layout|Project]], except that files can be "virtualized" by moving them to tape.  The files are still directly accessible, so this is a way to manage less-used files. On tape, they do not consume your disk quota, but can still be accessed if necessary.
+Nearline storage is like [[Project layout|Project]], except that files can be "virtualized" by moving them to tape.  This is a way to manage less-used files. On tape they do not consume your disk quota, but they can still be accessed, albeit more slowly.
-This is useful because the capacity of our tape libraries is both large and expandable.  When a file has been moved to tape (that is, "virtualized"), it will still appear in the <code>~/nearline</code> directory.  If the virtual file is read, the reading process will block for some period, probably a few minutes, while the file contents are read from tape to disk.  Then IO to the file will behave like a normal disk-based file.
+This is useful because the capacity of our tape libraries is both large and expandable.  When a file has been moved to tape (that is, "virtualized"), it will still appear in the directory listing.  If the virtual file is read, the reading process will block for some period, probably a few minutes, while the file contents are read from tape to disk.  Then IO to the file will behave like any other disk-based file.
 == Expected use ==