Filesystem

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Networked and cloud filesystems)
(Links)
Line 119: Line 119:
 
* [https://www.usenix.org/legacy/event/hotos09/tech/full_papers/seltzer/seltzer.pdf Hierarchical File Systems are Dead]
 
* [https://www.usenix.org/legacy/event/hotos09/tech/full_papers/seltzer/seltzer.pdf Hierarchical File Systems are Dead]
 
* [http://qanda.digipres.org/176/filesystem-checksums-value-digital-preservation-context Do filesystem-based checksums add value in a digital preservation context?]
 
* [http://qanda.digipres.org/176/filesystem-checksums-value-digital-preservation-context Do filesystem-based checksums add value in a digital preservation context?]
 +
* [http://lists.gnu.org/archive/html/coreutils/2014-08/msg00012.html My experience with using cp to copy a lot of files (432 millions, 39 TB)]

Revision as of 11:31, 12 September 2014

File Format
Name Filesystem
Ontology

{{{caption}}}

Filesystems are Electronic Formats that are a prerequisite to being able to read any file off a digital medium — you have to be able to mount the filesystem, and thus read it, in order to be able to read a file.

Contents

Single-system filesystems

(How files are organized on one system or device, such as a disk, tape, or flash memory; see next category for networked and cloud filesystems. Of course, any filesystem can be made available on a network to remote devices, but these are the native filesystems present on the storage device itself.)

Networked and cloud filesystems

(Used to make files available to multiple systems over a local or wide area network, including "on the cloud" via the Internet; systems access files through a protocol or API. The low-level storage details, usually concealed from end users and even most developers, may be within one or more of the single-device filesystems above, and the networked/cloud filesystem is generally defined independently of such details and might have very different characteristics and rules as to how the files are named, addressed, and structured.)

File content signature

(used to match files to a hash table or similar system in order to detect duplicates, help find specific files when their exact location is unknown, handle distributed networked filesystems, etc. See also Error detection and correction.)

Format details

Links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox