1,330
edits
Filesystems: Difference between revisions
→Ext4
m (→btrfs) |
(→Ext4) |
||
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This page serves to give some information on possible filesystems for Linux machines, in particular those that may be used for very large filesystems (many TB). The list is sorted by age! | This page serves to give some information on possible filesystems for Linux machines, in particular those that may be used for very large filesystems (many TB). The list is sorted by age! | ||
== XFS == | == XFS == | ||
* SGI's filesystem that was ported to Linux | * SGI's filesystem (1994) that was ported to Linux around 2001 | ||
* no 16 | * no 16 TB limitation; max size is 8 Eib (1 exbibyte = 2^60 bytes) | ||
* no compression and checksumming (data-integrity) features | * no data compression and checksumming (data-integrity) features. It does have metadata checksums. | ||
* the default for RHEL starting at version 7 | |||
== ZFS == | == ZFS == | ||
* Sun's filesystem which is natively available on Solaris and OpenSolaris (both of which are freely available) | * Sun's filesystem which is natively available on Solaris (since 2005)) and OpenSolaris (both of which are freely available) | ||
* no 16 TB limitation; max size is 2^128 bytes | |||
* (optional) transparent (gzip) compression (LZO compression available as patch) | * (optional) transparent (gzip) compression (LZO compression available as patch) | ||
* atomic updates - means that the on-disk state is consistent at all times, there's no need to perform a lengthy filesystem check after forced reboots/power failures | * atomic updates - means that the on-disk state is consistent at all times, there's no need to perform a lengthy filesystem check after forced reboots/power failures | ||
* background checksumming and self-healing for data integrity | * background checksumming and self-healing for data integrity | ||
* Built-in stripes (RAID-0), mirrors (RAID-1) and RAID-Z (it's like software RAID-5, but more efficient due to ZFS's copy-on-write transactional model) | * Built-in stripes (RAID-0), mirrors (RAID-1) and RAID-Z (it's like software RAID-5, but more efficient due to ZFS's copy-on-write transactional model) | ||
* there | * triple parity raid (raidz3) has been added to ZFS [http://blogs.sun.com/ahl/entry/triple_parity_raid_z] | ||
* the source code license of ZFS is incompatible with the GPL of the Linux kernel, therefore | * there is a port of ZFS to FreeBSD | ||
* | * the source code license of ZFS is incompatible with the GPL of the Linux kernel, therefore not in the latter | ||
* install from http://zfsonlinux.org/ | |||
== Ext4 == | == Ext4 == | ||
* | * ext4 is based on ext3 (same developers) | ||
* | * default of some Linux distros | ||
* no 16 | * no 16 TB limitation; max size is 1 EiB (1 exbibyte = 2^60 bytes) | ||
* no compression and checksumming (data-integrity) features | * no compression and checksumming (data-integrity) features | ||
== btrfs == | == btrfs == | ||
* latest addition to native Linux filesystems; considered stable since 2.6.31 kernel (http://www.h-online.com/open/Kernel-Log-2-6-31-Tracking--/features/113671) | * latest addition to native Linux filesystems; considered stable since 2.6.31 kernel (2009; see http://www.h-online.com/open/Kernel-Log-2-6-31-Tracking--/features/113671) | ||
* no 16 TB limitation; max size is 16 Eib (1 exbibyte = 2^60 bytes) | |||
* (optional) transparent (zlib) compression | * (optional) transparent (zlib) compression | ||
* checksumming for data integrity is implemented | * checksumming for data integrity is implemented | ||