Bureaucrats, cc_docs_admin, cc_staff
2,879
edits
Using nearline storage: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
==Nearline is a filesystem virtualized onto tape== | ==Nearline is a filesystem virtualized onto tape== | ||
Nearline storage is like [[Project layout|Project]], except that | Nearline storage is like [[Project layout|Project]], except that the system may "virtualize" files 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 directory listing. If the virtual file is read, the reading process will block for some time, 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. | 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 time, 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. | ||