Common filesystem features
|This article does not cite any sources. (December 2009) (Learn how and when to remove this template message)|
This is the glossary of the common filesystem features table.
The intention of this table is to provide an at-a-glance list of features and specifications for each filesystem.
- 1 Inventor
- 2 Name
- 3 Native operating system
- 4 Partition identificator
- 5 Bad sector allocation
- 6 File allocation
- 7 Directory structure
- 8 Namespace
- 9 Maximum filename size
- 10 Maximum files
- 11 Maximum volume size
- 12 Dates handled
- 13 Maximum date
- 14 Attributes
- 15 Named streams
- 16 Per-volume compression
- 17 Per-volume encryption
- 18 Per-file compression
- 19 Per-file encryption
- 20 Access control lists
List the names of those credited with the design of the filesystem specification. This should not include those responsible for writing the implementation.
The full, non abbreviated, name of the filesystem itself.
Native operating system
The name of the operating system in which this filesystem debuted.
The partitioning scheme and marker used to identify that a partition is formatted to this filesystem.
Bad sector allocation
Describe how the filesystem allocates and isolates bad sectors.
Describes how the filesystem allocates sectors in-use by files.
Describes how the subdirectories are implemented.
Lists the characters that are legal within file and directory names.
Maximum filename size
The maximum number of characters that a file or directory name may contain.
The maximum number of files the filesystem can handle.
Maximum volume size
The maximum size of a volume that the filesystem specification can handle. This may differ from the maximum size an operating system supports using a given implementation of the filesystem.
What type of dates and times the filesystem can support, which may include:
This is the date the file was “created” on the volume. This does not change when working normally with a file, e.g. opening, closing, saving, or modifying the file.
This is the date the file was last accessed. An access can be a move, an open, or any other simple access. It can also be tripped by Anti-virus scanners, or Windows system processes. Therefore, caution has to be used when stating a “file was last accessed by user XXX” if there is only the “File Access” date in NTFS to work from.
This date as shown by Windows there has been a change to the file itself. E.g. a notepad document is has more date added to it, would trip the date it was modified.
The date and time related attributes were modified. This may include ACLs and the file/directory name.
The date and time when the file was last backed up.
The maximum year that can be handled by the filesystem, as per the specification.
Lists the basic file attributes available.
Does the filesystem support real-time transparent compression and decompression of an entire volume.
Does the filesystem support real-time transparent encryption and decryption of an entire volume.
Does the filesystem support real-time transparent compression and decompression of individual files.
Does the filesystem support real-time transparent encryption and decryption of individual files.
Access control lists
Does the filesystem support multi-user access control lists (ACLs).