利用者:Puntti ja/sandbox/ファイルシステムの比較
表示
- この一覧は未完成です。加筆、訂正して下さる協力者を求めています。
ファイルシステムの比較では、ファイルシステムに関する一般情報および技術情報に関する比較を扱う。
一般情報
[編集]制限
[編集]ファイルシステム名 | ファイル名の最大長 | 使用可能な文字[注釈 4] | パスの最大長 | ファイルの最大サイズ | ボリュームの最大容量[注釈 5] | ファイルの最大数 |
---|---|---|---|---|---|---|
BeeGFS | 255 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 16 EiB | 16 EiB | ? |
CP/M file system | 8.3 | ASCII except for < > . , ; : = ? * [ ] | No directory hierarchy (but accessibility of files depends on user areas via USER command since CP/M 2.2) | 32 MiB | 512 MiB | ? |
IBM SFS | 8.8 | ? | ? | Non-hierarchical[13] | data-sort-type="number" data-sort-value="0" ? | ? |
DECtape | 6.3 | A–Z, 0–9 | DTxN:FILNAM.EXT = 15 | 369,280 バイト (577 * 640) | 369,920 バイト (578 * 640) | ? |
Elektronika BK tape format | 16 バイト | ? | No directory hierarchy | 64 KiB | Not limited. Approx. 800KB (one side) for 90 min cassette | ? |
MicroDOS file system | 14 バイト | ? | ? | 16 MiB | 32 MiB | ? |
Level-D | 6.3 | A–Z, 0–9 | DEVICE:FILNAM.EXT[PROJCT,PROGRM] = 7 + 10 + 15 = 32; + 5*7 for SFDs = 67 | 34,359,738,368 words (2**35-1); 206,158,430,208 SIXBIT バイト | Approx 12 GB (64 * 178 MB) | ? |
RT-11 | 6.3 | A–Z, 0–9, $ | 0 (no directory hierarchy) | 33,554,432 バイト (65536 * 512) | 33,554,432 バイト | ? |
Version 6 Unix file system (V6FS) | 14 バイト | Any byte except NUL and / [注釈 6]
|
No limit defined[注釈 7] | 16 MiB[注釈 8] | 32 MiB | ? |
Disk Operating System (GEC DOS) | ? | ? | ? | data-sort-type="number" data-sort-value="0" ? at least 131,072 バイト | data-sort-type="number" data-sort-value="0" ? | ? |
GEC DOS filing system extended | 8 バイト | A–Z, 0–9. Period was directory separator | ? No limit defined (workaround for OS limit) | data-sort-type="number" data-sort-value="0" ? at least 131,072 バイト | data-sort-type="number" data-sort-value="0" ? | ? |
CBM DOS | 16 バイト | Any byte except NUL | 0 (no directory hierarchy) | 16 MiB | 16 MiB | ? |
Version 7 Unix file system (V7FS) | 14 バイト | Any byte except NUL or / [注釈 6]
|
No limit defined[注釈 7] | 1 GiB[注釈 9] | 2 TiB | ? |
exFAT | 255 UTF-16 characters | ? | 32,760 Unicode characters with each path component no more than 255 characters[14] | 16 EiB[14] | 64 ZiB (276 バイト) | ? |
FAT (8-bit) | 6.3 (binary files) / 9 characters (ASCII files) | ASCII (0x00 and 0xFF not allowed in first character) | No directory hierarchy | data-sort-type="number" data-sort-value="0" ? | data-sort-type="number" data-sort-value="0" ? | ? |
FAT12/FAT16 | 8.3 (255 UCS-2 characters with LFN)[注釈 10] | SFN: OEM A-Z, 0-9, ! # $ % & ' ( ) - @ ^ _ ` { } ~, 0x80-0xFF, 0x20. LFN: Unicode except NUL, " * / : < > ? \ | [注釈 4][注釈 6] | No limit defined[注釈 7] | 32 MiB (4 GiB)[注釈 11] | 1 MiB to 32 MiB | ? |
FAT16B/FAT16X | 8.3 (255 UCS-2 characters with LFN)[注釈 10] | SFN: OEM A-Z, 0-9, ! # $ % & ' ( ) - @ ^ _ ` { } ~, 0x80-0xFF, 0x20. LFN: Unicode except NUL, " * / : < > ? \ | [注釈 4][注釈 10][注釈 6] | No limit defined[注釈 7] | 2 (4) GiB[注釈 11] | 16 MiB to 2 (4) GiB | ? |
FAT32/FAT32X | 8.3 (255 UCS-2 characters with LFN)[注釈 10] | SFN: OEM A-Z, 0-9, ! # $ % & ' ( ) - @ ^ _ ` { } ~, 0x80-0xFF, 0x20. LFN: Unicode except NUL, " * / : < > ? \ | [注釈 4][注釈 10][注釈 6] | 32,760 Unicode characters with each path component no more than 255 characters[14] | 4 GiB[14] | 512 MiB to 16 TiB[注釈 12] | ? |
FATX | 42 バイト[注釈 10] | ASCII. Unicode not permitted. | No limit defined[注釈 7] | 2 GiB | 16 MiB to 2 GiB | ? |
Fossil | ? | ? | ? | data-sort-type="number" data-sort-value="0" ? | data-sort-type="number" data-sort-value="0" ? | ? |
GEMDOS | 8.3 | A-Z, a-z, 0-9 ! @ # $ % ^ & ( ) + - = ~ ` ; ' " , < > | [ ] ( ) _[16] | ? | ? | ? | ? |
APFS | 255 UTF-8 characters | Unicode 9.0 encoded in UTF-8 [17] | ? | 8 EiB | data-sort-type="number" data-sort-value="0" ? | 263 [18] |
F2FS | 255 バイト | Any byte except NUL, /[注釈 6] | No limit defined[注釈 7] | 3.94 TiB | 16 TiB | ? |
MFS | 255 バイト | Any byte except :
|
No path (flat filesystem) | 256 MiB | 256 MiB | ? |
HFS | 31 バイト | Any byte except :
|
Unlimited | 2 GiB | 2 TiB | ? |
HPFS | 255 バイト | Any byte except NUL[注釈 13] | No limit defined[注釈 7] | 2 GiB | 2 TiB[注釈 14] | ? |
NTFS | 255 characters | In Win32 namespace: any UTF-16 code unit (case-insensitive) except /\:*"?<>| as well as NUL
In POSIX namespace: any UTF-16 code unit (case-sensitive) except |
32,767 Unicode characters with each path component (directory or filename) up to 255 characters long[注釈 7] | 16 EiB[注釈 15] | 16 EiB[注釈 15] | ? |
ReFS | 255 UTF-16 characters[20] | Any Unicode except NUL, / [20]
|
32,767 Unicode characters with each path component (directory or filename) up to 255 characters long[20] | 16 EiB[20] | 3.76 ZiB[21] | ? |
HFS Plus | 255 UTF-16 characters[注釈 16] | Any valid Unicode[注釈 6][注釈 17] | Unlimited | slightly less than 8 EiB | slightly less than 8 EiB[22][23] | ? |
FFS | 255 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 4 GiB | 256 TiB | ? |
HAMMER | 255 バイト[24] | Any byte except NUL[注釈 6] | ? | data-sort-type="number" data-sort-value="0" ? | 1 EiB[25] | ? |
UFS1 | 255 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 16 GiB to 256 TiB | 16 EiB | ? |
UFS2 | 255 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 512 GiB to 32 PiB | 512 ZiB[26] (279 バイト) | ? |
ext | 255 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 2 GiB | 2 GiB | ? |
Xiafs | 248 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 64 MiB | 2 GiB | ? |
ext2 | 255 バイト | Any byte except NUL, /[注釈 6] | No limit defined[注釈 7] | 16 GiB to 2 TiB[注釈 5] | 2 TiB to 32 TiB | ? |
ext3 | 255 バイト | Any byte except NUL, /[注釈 6] | No limit defined[注釈 7] | 16 GiB to 2 TiB[注釈 5] | 2 TiB to 32 TiB | ? |
ext4 | 255 バイト | Any byte except NUL, /[注釈 6] | No limit defined[注釈 7] | 16 GiB to 16 TiB[注釈 5][27] | 1 EiB | 232 |
NOVA | 255 バイト | Any byte except NUL, /[注釈 6] | No limit defined[注釈 7] | 16 EiB | 16 EiB | ? |
Lustre | 255 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 16 EiB on ZFS | 16 EiB | ? |
GPFS | 255 UTF-8 codepoints | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | No limit found | 299 バイト (2 PiB tested) | ? |
GFS | 255 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 2 TiB to 8 EiB[注釈 18] | 2 TiB to 8 EiB[注釈 18] | ? |
NILFS | 255 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 8 EiB | 8 EiB | ? |
ReiserFS | 4,032 バイト/255 characters | Any byte except NUL or '/' [注釈 6]
|
No limit defined[注釈 7] | 8 TiB[注釈 19] (v3.6), 4 GiB (v3.5) | 16 TiB | ? |
Reiser4 | 3,976 バイト | Any byte except / and NUL
|
No limit defined[注釈 7] | 8 TiB on x86 | data-sort-type="number" data-sort-value="0" ? | ? |
OCFS | 255 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 8 TiB | 8 TiB | ? |
OCFS2 | 255 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 4 PiB | 4 PiB | ? |
XFS | 255 バイト[注釈 20] | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 8 EiB[注釈 21] | 8 EiB[注釈 21] | ? |
JFS1 | 255 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 8 EiB | 512 TiB to 4 PiB | ? |
JFS | 255 バイト | Any Unicode except NUL | No limit defined[注釈 7] | 4 PiB | 32 PiB | ? |
QFS | 255 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 16 EiB[注釈 22] | 4 PiB[注釈 22] | ? |
BFS | 255 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 12,288 バイト to 260 GiB[注釈 23] | 256 PiB to 2 EiB | ? |
AdvFS | 255 characters | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 16 TiB | 16 TiB | ? |
NSS | 256 characters | Depends on namespace used[注釈 24] | Only limited by client | 8 TiB | 8 TiB | ? |
NWFS | 80 バイト[注釈 25] | Depends on namespace used[注釈 24] | No limit defined[注釈 7] | 4 GiB | 1 TiB | ? |
ODS-5 | 236 バイト[注釈 26] | ? | 4,096 バイト[注釈 27] | 1 TiB | 1 TiB | ? |
VxFS | 255 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 16 EiB | data-sort-type="number" data-sort-value="0" ? | ? |
UDF | 255 バイト | Any Unicode except NUL | 1,023 バイト[注釈 28] | 16 EiB | 512 MiB to 16 TiB | ? |
ZFS | 255 バイト | Any Unicode except NUL | No limit defined[注釈 7] | 16 EiB | 256 ZiB (278 バイト) | 2128 |
Btrfs | 255 バイト | Any byte except '/' and NUL | No limit defined | 16 EiB | 16 EiB | 264 |
Minix V1 FS | 14 or 30 バイト, set at filesystem creation time | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 256.5 MiB [注釈 29] | 64 MiB | ? |
Minix V2 FS | 14 or 30 バイト, set at filesystem creation time | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 2 GiB [注釈 29] | 1 GiB | ? |
Minix V3 FS | 60 バイト | Any byte except NUL[注釈 6] | No limit defined[注釈 7] | 2 GiB | 4 GiB | ? |
VMFS2 | 128 | Any byte except NUL or / [注釈 6]
|
2,048 | 4 TiB[注釈 30] | 64 TiB | ? |
VMFS3 | 128 | Any byte except NUL or / [注釈 6]
|
2,048 | 2 TiB[注釈 30] | 64 TiB | ? |
ISO 9660:1988 | Level 1: 8.3, Level 2 & 3: ~ 180 |
Depends on Level[注釈 31] | ~ 180 バイト? | 4 GiB (Level 1 & 2) to 8 TiB (Level 3)[注釈 32] | 8 TiB[注釈 33] | ? |
Joliet ("CDFS") | 64 Unicode characters | All UCS-2 code except *, /, \, :, ;, and ?[29] | ? | same as ISO 9660:1988 | same as ISO 9660:1988 | ? |
Rock Ridge | 255 バイト | Any byte except NUL or /[注釈 6] | No limit defined[注釈 7] | same as ISO 9660:1988 | same as ISO 9660:1988 | ? |
UniFS | No limit defined (depends on client) | ? | No limit defined (depends on client) | Available cache space at time of write (depends on platform) | No limit defined | No limit defined |
ISO 9660:1999 | ? | ? | ? | data-sort-type="number" data-sort-value="0" ? | data-sort-type="number" data-sort-value="0" ? | ? |
High Sierra Format | ? | ? | ? | data-sort-type="number" data-sort-value="0" ? | data-sort-type="number" data-sort-value="0" ? | ? |
SquashFS | ? | ? | No limit defined | 16 EiB | 16 EiB | ? |
File system | Maximum filename length | Allowable characters in directory entries[注釈 4] | Maximum pathname length | Maximum file size | Maximum volume size[注釈 5] | Max number of files |
メタデータ
[編集]ファイル名 | 所有者情報 | POSIXファイルパーミッション | 作成日時タイムスタンプ | 最終アクセス日時タイムスタンプ | メタデータ最終変更日時タイムスタンプ | 最終アーカイブタイムスタンプ | アクセスコントロールリスト | セキュリティ/ MACラベル | 拡張ファイル属性/代替データストリーム/フォーク | チェックサム/ECC |
---|---|---|---|---|---|---|---|---|---|---|
BeeGFS | Yes | Yes | No | Yes | Yes | No | Yes | ? | Yes | Yes |
CP/M file system | No | No | Yes[注釈 34] | No | No | No | No | No | No | No |
DECtape[30] | No | No | Yes | No | No | No | No | No | No | No |
Elektronika BK tape format | No | No | No | No | No | No | No | No | No | Yes |
Level-D | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No |
RT-11[31] | No | No | Yes (date only) | No | No | No | No | No | No | Yes |
Version 6 Unix file system (V6FS)[32] | Yes | Yes | No | Yes | No | No | No | No | No | No |
Version 7 Unix file system (V7FS)[33] | Yes | Yes | No | Yes | No | No | No | No | No | No |
FAT12/FAT16/FAT32 | No | No | Yes | Yes | No[注釈 35] | No | No | No | No[注釈 36] | No |
HPFS | Yes[注釈 37] | No | Yes | Yes | No | No | No | ? | Yes | No |
NTFS | Yes | Yes[注釈 38] | Yes | Yes | Yes | No | Yes | Yes[注釈 39] | Yes | No |
ReFS | Yes | Yes | Yes | Yes | Yes | No | Yes | ? | Yes[注釈 40] | Yes[注釈 41] |
HFS | No | No | Yes | No | No | Yes | No | No | Yes | No |
HFS Plus | Yes | Yes | Yes | Yes | Yes | Yes | Yes | ? | Yes | No |
FFS | Yes | Yes | No | Yes | Yes | No | No | No | No | No |
UFS1 | Yes | Yes | No | Yes | Yes | No | Yes[注釈 42] | Yes[注釈 42] | No[注釈 43] | No |
UFS2 | Yes | Yes | Yes | Yes | Yes | No | Yes[注釈 42] | Yes[注釈 42] | Yes | No |
HAMMER | ? | ? | ? | ? | ? | ? | ? | ? | ? | ? |
LFS | Yes | Yes | No | Yes | Yes | No | No | No | No | No |
ext | Yes | Yes | No | No | No | No | No | No | No | No |
Xiafs | Yes | Yes | No | Yes | Yes | No | No | No | No | No |
ext2 | Yes | Yes | No | Yes | Yes | No | Yes[注釈 44] | Yes[注釈 44] | Yes | No |
ext3 | Yes | Yes | No | Yes | Yes | No | Yes[注釈 44] | Yes[注釈 44] | Yes | No |
ext4 | Yes | Yes | Yes | Yes | Yes | No | Yes[注釈 44] | Yes[注釈 44] | Yes | 部分的[注釈 45] |
NOVA | Yes | Yes | Yes | Yes | Yes | No | No | No | No | Yes |
Lustre | Yes | Yes | No | Yes | Yes | No | Yes | Yes | Yes | No |
F2FS | Yes | Yes | Yes | Yes | Yes | No | Yes[注釈 44] | Yes[注釈 44] | Yes | No |
GPFS | Yes | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | Yes |
GFS | Yes | Yes | No | Yes | Yes | No | Yes[注釈 44] | Yes[注釈 44] | Yes | No |
NILFS | Yes | Yes | Yes | No | Yes | No | No | No | No | Yes |
ReiserFS | Yes | Yes | No | Yes | Yes | No | Yes[注釈 44] | Yes[注釈 44] | Yes | No |
Reiser4 | Yes | Yes | No | Yes | Yes | No | No | No | No | No |
OCFS | No | Yes | No | No | Yes | Yes | No | No | No | No |
OCFS2 | Yes | Yes | No | Yes | Yes | No | No | No | No | No |
XFS | Yes | Yes | 部分的[注釈 46] | Yes | Yes | No | Yes | Yes[注釈 44] | Yes | 部分的[注釈 47] |
TFS | ? | ? | ? | ? | ? | ? | ? | ? | ? | Yes |
JFS | Yes | Yes | Yes | Yes | Yes | No | Yes | Yes | Yes | No |
QFS | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | No |
BFS | Yes | Yes | Yes | No | No | No | No | No | Yes | No |
AdvFS | Yes | Yes | No | Yes | Yes | No | Yes | No | Yes | No |
NSS | Yes | Yes | Yes[注釈 48] | Yes[注釈 48] | Yes | Yes[注釈 48] | Yes | ? | Yes[注釈 49][注釈 50] | No |
NWFS | Yes | ? | Yes[注釈 48] | Yes[注釈 48] | Yes | Yes[注釈 48] | Yes | ? | Yes[注釈 49][注釈 50] | No |
ODS-5 | Yes | Yes | Yes | ? | ? | Yes | Yes | ? | Yes[注釈 51] | No |
APFS | Yes | Yes | Yes | Yes | Yes | Yes | Yes | ? | Yes | 部分的 |
VxFS | Yes | Yes | Yes | Yes | Yes | No | Yes | ? | Yes[注釈 44] | No |
UDF | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No | Yes | No |
Fossil | Yes | Yes[注釈 52] | No | Yes | Yes | No | No | No | No | No |
ZFS | Yes | Yes | Yes | Yes | Yes | Yes | Yes | No[注釈 53] | Yes[注釈 54] | Yes |
Btrfs | Yes | Yes | Yes | Yes | ? | ? | Yes | Yes | Yes | Yes[注釈 55] |
Minix V1 | Yes | Yes | No | No | No | No | No | No | No | No |
Minix V2 | Yes | Yes | No | Yes | Yes | No | No | No | No | No |
Minix V3 | Yes | Yes | No | Yes | Yes | No | No | No | No | No |
VMFS2 | Yes | Yes | No | Yes | Yes | No | No | No | No | No |
VMFS3 | Yes | Yes | No | Yes | Yes | No | No | No | No | No |
ISO 9660:1988 | No | No | Yes | No | No | No | No | No | No | No |
Rock Ridge | Yes | Yes | No | Yes[注釈 56] | Yes | No | No[注釈 57] | No[注釈 58] | No[注釈 58] | No |
Joliet ("CDFS") | No | No | Yes | No | No | No | No | No | No | No |
ISO 9660:1999 | No | No | Yes | No | No | No | No | No | No | No |
High Sierra | No | No | Yes | No | No | No | No | No | No | No |
SquashFS | Yes | Yes | Yes | Yes | Yes | ? | Yes | No | Yes | No |
File system | Stores file owner | POSIX file permissions | Creation timestamps | Last access/read timestamps | Last metadata change timestamps | Last archive timestamps | Access control lists | Security/ MAC labels | Extended attributes/ Alternate data streams/ forks | Checksum/ ECC |
機能
[編集]ファイル
[編集]ファイルシステム名 | ハードリンク | シンボリックリンク | [[ジャーナリングファイルシステム|ブロックジャーナリング] | メタデータのみのジャーナリング | ケースセンシティブ | ケースプリザービング | ファイル変更履歴 | 内部スナップショット/ブランチング | XIP | ファイルシステムレベルの暗号化 | データ重複排除 | 並列実行 | TRIMのサポート | データのチェックサム |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
DECtape | No | No | No | No | No | No | No | No | No | No | No | ? | ? | No |
BeeGFS | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No | No | Yes | ? | ? | No |
Level-D | No | No | No | No | No | No | No | No | No | No | No | ? | ? | No |
RT-11 | No | No | No | No | No | No | No | No | No | No | No | ? | ? | No |
APFS | Yes | Yes | ? | ? | 部分的 | Yes | ? | Yes | ? | Yes | 部分的 | ? | Yes[36][37] | No |
Version 6 Unix file system (V6FS) | Yes | No | No | No | Yes | Yes | No | No | No | No | No | ? | ? | No |
Version 7 Unix file system (V7FS) | Yes | No[注釈 59] | No | No | Yes | Yes | No | No | No | No | No | ? | ? | No |
FAT12 | No | No | No | 部分的 (with TFAT12 only) | No | 部分的 (with VFAT LFNs only) | No | No | No | 部分的 (DR-DOS with SECURITY only) | No | ? | ? | No |
FAT16 / FAT16B / FAT16X | No | No | No | 部分的 (with TFAT16 only) | No | 部分的 (with VFAT LFNs only) | No | No | No | 部分的 (DR-DOS with SECURITY only) | No | ? | ? | No |
FAT32 / FAT32X | No | No | No? | 部分的 (with TFAT32 only) | No | 部分的 (with VFAT LFNs only) | No | No | No | No | No | ? | Yes (linux) | No |
GFS | Yes | Yes[注釈 60] | Yes | Yes[注釈 61] | Yes | Yes | No | No | No | No | ? | ? | Yes (linux) | No |
HPFS | No | No | No | No | No | Yes | No | ? | No | No | ? | ? | ? | No |
NTFS | Yes | Yes[注釈 62] | No[注釈 63] | Yes[注釈 63] (2000) | Yes[注釈 64] | Yes | Yes | 部分的[注釈 65] | ? | Yes | Yes[注釈 66][39] | ? | Yes (windows 7+) | No |
HFS Plus | Yes[40] | Yes | No | Yes[注釈 67] | 部分的[注釈 68] | Yes | Yes[注釈 69] | No | No | No[注釈 70] | No | ? | Yes | No |
FFS | Yes | Yes | No | No | Yes | Yes | No | No | No | No | No | ? | ? | No |
UFS1 | Yes | Yes | No | No | Yes | Yes | No | No | No | No | No | ? | ? | No |
UFS2 | Yes | Yes | No | No[注釈 71] | Yes | Yes | No | Yes | ? | No | No | ? | ? | No |
HAMMER | Yes | Yes | Yes | Yes | Yes | Yes | ? | Yes | No | No | Yes | ? | ? | Yes |
LFS | Yes | Yes | Yes[注釈 72] | No | Yes | Yes | No | Yes | No | No | No | ? | ? | No |
ext | Yes | Yes | No | No | Yes | Yes | No | No | No | No | No | ? | ? | No |
Xiafs | Yes | Yes | No | No | Yes | Yes | No | No | No | No | No | ? | ? | No |
ext2 | Yes | Yes | No | No | Yes | Yes | No | No | Yes[注釈 73] | No | No | ? | ? | No |
ext3 | Yes | Yes | Yes (2001) [注釈 74] | Yes (2001) | Yes | Yes | No | No | Yes | No | No | ? | 部分的 linux, by default-offline only | No |
ext4 | Yes | Yes | Yes[注釈 74] | Yes | Yes | Yes | No | No | Yes | Yes, experimental [45] | No | ? | Yes (linux) | No |
NOVA | Yes | Yes | No | Yes | Yes | Yes | No | Yes | Yes | No | No | ? | ? | Yes |
F2FS | Yes | Yes | Yes[注釈 72] | No | Yes | Yes | No | No | No | Yes, experimental [46] | No | ? | ? | No |
Lustre | Yes | Yes | Yes[注釈 74] | Yes | Yes | Yes | No | No | No | No | No | ? | ? | No |
NILFS | Yes | Yes | Yes[注釈 72] | No | Yes | Yes | No | Yes | No | No | No | ? | ? | Yes |
ReiserFS | Yes | Yes | Yes[注釈 75] | Yes | Yes | Yes | No | No | ? | No | No | ? | ? | No |
Reiser4 | Yes | Yes | Yes | No | Yes | Yes | No | ? | ? | Yes[注釈 76] | ? | ? | ? | No |
OCFS | No | Yes | No | No | Yes | Yes | No | No | No | No | No | ? | ? | No |
OCFS2 | Yes | Yes | Yes | Yes | Yes | Yes | No | No | No | No | No | ? | ? | No |
XFS | Yes | Yes | Yes | Yes | Yes[注釈 77] | Yes | Yes | No | ? | No | Yes, experimental [47] | ? | Yes (linux) | No |
JFS | Yes | Yes | Yes | Yes (1990) | Yes[注釈 78] | Yes | No | ? | ? | No | ? | ? | Yes (linux) | No |
QFS | Yes | Yes | No | Yes | Yes | Yes | No | No | No | No | No | ? | ? | No |
BFS | Yes | Yes | No | Yes | Yes | Yes | ? | No | No | No | No | ? | 部分的 (Haiku) | No |
NSS | Yes | Yes | ? | Yes | Yes[注釈 79] | Yes[注釈 79] | Yes[注釈 80] | Yes | No | Yes | ? | ? | ? | No |
NWFS | Yes[注釈 81] | Yes[注釈 81] | No | No | Yes[注釈 79] | Yes[注釈 79] | Yes[注釈 80] | ? | No | No | ? | ? | ? | No |
ODS-2 | Yes | Yes[注釈 82] | No | Yes | No | No | Yes | Yes | No | No | No | ? | ? | No |
ODS-5 | Yes | Yes[注釈 82] | No | Yes | No | Yes | Yes | Yes | ? | No | No | ? | ? | No |
UDF | Yes | Yes | Yes[注釈 72] | Yes[注釈 72] | Yes | Yes | No | No | Yes | No | No | ? | ? | No |
VxFS | Yes | Yes | Yes | No | Yes | Yes | Yes | Yes[注釈 83] | ? | No | Yes | ? | ? | No |
Fossil | No | No | No | No | Yes | Yes | Yes | Yes | No | No | Yes | ? | ? | No |
ZFS | Yes | Yes | Yes[注釈 84] | No[注釈 84] | Yes | Yes | No | Yes | No | Yes[注釈 85] | Yes | ? | Yes (FreeBSD) | Yes |
Btrfs | Yes | Yes | Yes | Yes | Yes | Yes | ? | Yes | ? | No, planned, not being developed (Nov, 2015)[51] | Yes | ? | Yes (linux) | Yes |
TFS | ? | ? | ? | ? | ? | ? | ? | Yes | ? | ? | ? | Yes [52] | Yes (redox OS)[53] | Yes |
Minix V1 | Yes | Yes | No | No | Yes | Yes | No | No | No | No | No | ? | ? | No |
Minix V2 | Yes | Yes | No | No | Yes | Yes | No | No | No | No | No | ? | ? | No |
Minix V3 | Yes | Yes | No | No | Yes | Yes | No | No | No | No | No | ? | ? | No |
VMFS2 | Yes | Yes | No | Yes | Yes | Yes | No | No | No | No | No | ? | ? | No |
VMFS3 | Yes | Yes | No | Yes | Yes | Yes | No | No | No | No | No | ? | ? | No |
ReFS | No | Yes | ? | ? | Yes[注釈 64] | Yes | ? | ? | ? | No | No | ? | ? | Yes |
ISO 9660 | No | No | No | No | No | No | No | No | No | No | No[注釈 86] | ? | ? | No |
Rock Ridge | Yes | Yes | No | No | Yes | Yes | No | No | No | No | No[注釈 86] | ? | ? | No |
Joliet ("CDFS") | No | No | No | No | No | Yes | No | No | No | No | No[注釈 86] | ? | ? | No |
SquashFS | No | No | No | No | Yes | Yes | No | No | No | No | Yes | ? | ? | No |
File system | Hard links | Symbolic links | Block journaling | Metadata-only journaling | Case-sensitive | Case-preserving | File Change Log | Internal snapshotting / branching | XIP | Filesystem-level encryption | Data deduplication | Concurrent execution | Trim support | Data checksums |
リサイズの可否
[編集]ファイルシステム | ホストOS | オンラインでの増量 | オフラインでの増量 | オンラインでの減量 | オフラインでの減量 |
---|---|---|---|---|---|
Btrfs[54] | Linux | Yes | Yes | Yes | Yes |
ext2[55] | Linux | No | Yes | No | Yes |
ext3[55] | Linux | Yes | Yes | No | Yes |
ext4[55] | Linux | Yes | Yes | No | Yes |
NOVA | Linux | No | No | No | No |
FAT12 | misc. | No | with third-party tools[56] | No | with third-party tools[56] |
FAT16 / FAT16B / FAT16X | misc. | No | with third-party tools[56] | No | with third-party tools[56] |
FAT32 / FAT32X | misc. | No | with third-party tools[56] | No | with third-party tools[56] |
F2FS[57] | Linux | No | Yes | No | No |
HFS+ | Linux | No | No | No | No |
HFS+ | macOS | Yes | No | Yes | No |
JFS[58] | Linux | No | Yes | No | No |
JFS2 | AIX | Yes | ? | Yes | ? |
Lustre[59] | Linux | Yes | ? | No | No |
NILFS[60] | Linux | Yes | No | Yes | No |
NTFS[61] | Linux | No | Yes | No | Yes |
NTFS | Windows | Yes | Yes | Yes | Yes |
APFS | macOS | ? | ? | ? | ? |
ZFS | misc. | Yes | No | No | No |
Reiser4[62] | Linux | Yes | Yes | No | Yes |
ReiserFS[63] | Linux | Yes | Yes | No | Yes |
XFS[64] | Linux | Yes | No | No | No |
ReFS | Windows | Yes | ? | No | ? |
UFS2[65] | FreeBSD | Yes (FreeBSD 10.0-RELEASE or later) | Yes | No | No |
HAMMER | DragonflyBSD | ? | ? | ? | ? |
SquashFS | Linux | No | No | No | No |
アロケーションおよび配置のポリシー
[編集]ファイルシステム名 | テールパッキング | 透過的圧縮 | ブロックサブアロケーション | 遅延書き込み | Extent | 可変ブロック長[注釈 87] | スパースファイル | コピーオンライト |
---|---|---|---|---|---|---|---|---|
DECtape | No | No | No | No | No | No | No | No |
BeeGFS | No | Yes (e.g. with zfs) | No | Yes | Yes | Yes | Yes | Yes (e.g. with zfs) |
Level-D | No | No | No | No | Yes | No | No | No |
APFS | ? | No | ? | Yes | Yes | ? | Yes | Yes |
Version 6 Unix file system (V6FS) | No | No | No | No | No | No | Yes | ? |
Version 7 Unix file system (V7FS) | No | No | No | No | No | No | Yes | ? |
FAT12 | No | 部分的[注釈 88] | 部分的 (only inside of Stacker 3/4 and DriveSpace 3 compressed volumes[66]) | No | 部分的 (only inside of compressed volumes)[67] | No | 部分的 (only inside of compressed volumes)[68] | No |
FAT16 / FAT16B / FAT16X | No | 部分的[注釈 88] | 部分的 (only inside of Stacker 3/4 and DriveSpace 3 compressed volumes[66]) | No | 部分的 (only inside of compressed volumes)[67] | No | 部分的 (only inside of compressed volumes)[68] | No |
FAT32 / FAT32X | No | No | No | No | No | No | No | No |
GFS | 部分的[注釈 89] | No | No | No | No | No | Yes | ? |
HPFS | No | No | No | No | Yes | No | No | ? |
NTFS | No | Yes | 部分的 | No | Yes | No | Yes | ? |
HFS Plus | No | No | No | No | Yes | No | No | ? |
FFS | No | No | 8:1[注釈 90] | No | No | No | Yes | ? |
UFS1 | No | No | 8:1[注釈 90] | No | No | No | Yes | ? |
UFS2 | No | No | 8:1[注釈 90] | No | No | Yes | Yes | ? |
LFS | No | No | 8:1[注釈 90] | No | No | No | Yes | Yes |
ext | No | No | No | No | No | No | Yes | No |
Xiafs | No | No | No | No | No | No | Yes | ? |
ext2 | No | No[注釈 91] | No[注釈 92] | No | No | No | Yes | No |
ext3 | No | No | No[注釈 92] | No | No | No | Yes | No |
ext4 | No | No | No[注釈 92] | Yes | Yes | No | Yes | No |
NOVA | No | No | No | No | Yes | No | Yes | Yes |
F2FS | No | No | No | Yes | 部分的[注釈 93] | No | Yes | Yes |
Lustre | No | No | No | Yes | Yes | No | Yes | ? |
NILFS | No | No | No | Yes | No | No | Yes | Yes |
ReiserFS | Yes | No | Yes[注釈 94] | No | No | No | Yes | ? |
Reiser4 | Yes | Yes[注釈 76] | Yes[注釈 94] | Yes | Yes[注釈 95] | No | Yes | ? |
OCFS | No | No | No | No | Yes | No | ? | ? |
OCFS2 | No | No | No | No | Yes | No | Yes | ? |
XFS | No | No | No | Yes | Yes | No | Yes | Yes, on request[69] |
TFS | Yes | Yes | ||||||
JFS | No | only in JFS1 on AIX[70] | Yes | No | Yes | No | Yes | ? |
QFS | No | No | Yes | No | No | No | ? | ? |
BFS | No | No | No | No | Yes | No | ? | ? |
NSS | No | Yes | No | No | Yes | No | ? | ? |
NWFS | No | Yes | Yes[注釈 96] | No | No | No | ? | ? |
ODS-5 | No | No | No | No | Yes | No | ? | ? |
VxFS | No | No | ? | No | Yes | No | Yes | ? |
UDF | No | No | No | ?[注釈 97] | Yes | No | No | ? |
Fossil | No | Yes | No | No | No | No | ? | ? |
ZFS | No | Yes | Yes | Yes | No | Yes | Yes | Yes |
Btrfs | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
VMFS2 | No | No | Yes | No | No | No | Yes | ? |
VMFS3 | No | No | Yes | No | No | No | Yes | ? |
ReFS | ? | No | ? | ? | ? | No | Yes | Yes |
ISO 9660 | No | No[注釈 98] | No | No | Yes[注釈 99] | No | No | No |
Rock Ridge | No | No[注釈 98] | No | No | Yes[注釈 99] | No | No | No |
Joliet ("CDFS") | No | No[注釈 98] | No | No | Yes[注釈 99] | No | No | No |
SquashFS | No | Yes | No | No | No | No | Yes | No |
File system | Tail packing | Transparent compression | Block suballocation | Allocate-on-flush | Extents | Variable file block size[注釈 87] | Sparse files | Copy on write |
OSサポート
[編集]ファイルシステム名 | DOS | Windows 9x | Windows NT | Linux | Classic Mac OS | macOS | FreeBSD | OS/2 | BeOS | Minix | Solaris | z/OS |
---|---|---|---|---|---|---|---|---|---|---|---|---|
APFS | No | No | No | No | No | Yes (Since macOS Sierra) |
No | No | No | No | No | No |
BeeGFS | No | No | No | Yes | No | ? | No | No | ? | ? | ? | No |
DECtape | No | No | No | No | No | No | No | No | No | No | No | No |
Level-D | No | No | No | ? | No | ? | No | No | No | No | ? | ? |
RT-11 | No | No | No | No | No | No | No | No | No | No | No | No |
Version 6 Unix file system (V6FS) | No | No | No | ? | No | ? | No | No | ? | ? | ? | ? |
Version 7 Unix file system (V7FS) | No | No | No | Yes | No | ? | No | No | ? | ? | ? | ? |
FAT12 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | 部分的 (via dosdir, dosread, doswrite) | Yes | ? |
FAT16 / FAT16B / FAT16X | Yes (FAT16 from DOS 3.0, FAT16B from DOS 3.31, FAT16X from DOS 7.0) | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | 部分的 (via dosdir, dosread, doswrite, not FAT16X) | Yes | ? |
FAT32 / FAT32X | Yes (from DOS 7.10) | Yes (from Windows 95 OSR2) | Yes (from Windows 2000) | Yes | Yes? | Yes | Yes | Yes | Yes | No | Yes | ? |
GFS | No | No | No | Yes | No | ? | No | ? | ? | ? | ? | ? |
HPFS | 部分的 (with third-party drivers) | No | 部分的 (with NT 3.1 to 4.0 only) | Yes | ? | ? | Yes | Yes (from OS/2 1.2) | ? | No | ? | ? |
NTFS | 部分的 (with third-party drivers) | Yes (with 3rd-party drivers like “Paragon NTFS for Win98”,“DiskInternals NTFS Reader”) | Yes | Yes with ntfs-3g | No | Yes natively read only, write support with Paragon NTFS or ntfs-3g | Yes with ntfs-3g | ? | Yes with ntfs-3g | No | Yes with ntfs-3g | ? |
Apple HFS | No | No | Yes with Paragon HFS+ [71] | Yes | Yes | Yes | No | ? | Yes | No | ? | No |
Apple HFS Plus | No | No | Yes with Paragon HFS+ [71] | 部分的 - writing support only to unjournalled FS | Yes from Mac OS 8.1 | Yes | No | ? | with addon | No | ? | No |
FFS | No | No | ? | ? | ? | Yes | Yes | ? | ? | ? | ? | ? |
UFS1 | No | No | 部分的 (with ufs2tools, read only) | 部分的 - read only | ? | Yes | Yes | No | ? | ? | Yes | ? |
UFS2 | No | No | 部分的 (with ufs2tools, read only) | Yes | ? | Yes | Yes | No | ? | ? | ? | ? |
LFS | No | No | No | ? | ? | ? | No | No | ? | ? | ? | ? |
ext | No | No | No | Yes - until 2.1.20 | No | No | No | No | No | No | No | No |
Xiafs | No | No | No | Yes - until 2.1.20 |
No | No | No | No | No | No | No | No |
ext2 | No | No | Yes with Paragon ExtFS [74] or partial with Ext2 IFS[75] or ext2fsd[76] | Yes | No | Yes with Paragon ExtFS [77] or ext2fsx | Yes | No | Yes | ? | ? | ? |
ext3 | No | No | Yes with Paragon ExtFS [74] or partial with Ext2 IFS[75] or ext2fsd[76] | Yes | 部分的 (read only)[要出典] | Yes with Paragon ExtFS [77] or partial with ext2fsx (journal not updated on writing) | 部分的 (read-only)[78][79] | No | with addon | ? | Yes | ? |
ext4 | No | No | Yes with Paragon ExtFS [74] or partial with Ext2 IFS[75] or ext2fsd[76] | Yes | ? | Yes with Paragon ExtFS [77] | 部分的 support in kernel since version 10.1 (read-only)[78][79] | No | with addon | ? | ? | ? |
NOVA | No | No | No | Yes | No | No | No | No | No | No | No | No |
Lustre | No | No | No | Yes[80] | ? | ? | No | ? | ? | ? | Yes | ? |
NILFS | No | No | ? | Yes as an external kernel module | ? | ? | No | ? | ? | ? | ? | ? |
F2FS | No | No | No | Yes | No | No | No | No | No | No | No | No |
ReiserFS | No | No | No | Yes | ? | ? | 部分的 Read Only | ? | with addon | ? | ? | ? |
Reiser4 | No | No | No | Yes with a kernel patch | ? | ? | No | ? | ? | ? | ? | ? |
SpadFS | No | No | No | Yes | No | No | ? | No | No | No | No | No |
OCFS | No | No | No | Yes | ? | ? | No | No | ? | ? | ? | ? |
OCFS2 | No | No | No | Yes | ? | ? | No | No | ? | ? | ? | ? |
XFS | No | No | No | Yes | ? | ? | 部分的 | ? | with addon (read only) | ? | ? | ? |
TFS | No | No | No | ? | No | No | ? | No | No | No | No | No |
JFS | No | No | No | Yes | ? | ? | No | Yes | ? | ? | ? | ? |
QFS | No | No | No | 部分的 - client only[81] | ? | ? | No | No | ? | ? | Yes | ? |
Be File System | No | No | No | 部分的 - read-only | ? | ? | No | No | Yes | ? | ? | ? |
NSS | No | No | No | Yes via EVMS[注釈 100] | ? | ? | No | No | ? | ? | ? | ? |
NWFS | 部分的 (with Novell drivers) | No | No | ? | ? | ? | Yes | No | ? | ? | ? | ? |
ODS-2 | No | No | No | ? | ? | ? | No | No | ? | ? | ? | ? |
ODS-5 | No | No | No | ? | ? | ? | No | No | ? | ? | ? | ? |
UDF | No | ? | Yes | Yes | ? | Yes | Yes | ? | ? | ? | Yes | ? |
VxFS | No | No | No | Yes | ? | ? | No | No | ? | ? | Yes | ? |
Fossil | No | No | No | Yes[注釈 101] | No | Yes[注釈 101] | Yes[注釈 101] | No | No | No | Yes[注釈 101] | ? |
ZFS | No | No | No | Yes with FUSE[82] or as an external kernel module[83] | ? | Yes with Read/Write Developer Preview[84] | Yes | ? | ? | ? | Yes | ? |
Btrfs | No | No | 部分的 with WinBtrfs[85] | Yes | ? | ? | ? | ? | ? | ? | ? | ? |
VMFS2 | No | No | No | ? | ? | ? | No | No | ? | ? | ? | ? |
VMFS3 | No | No | No | ? | ? | ? | No | No | ? | ? | ? | ? |
IBM HFS | No | No | No | No | No | No | No | No | No | No | No | Yes |
IBM zFS | No | No | No | No | No | No | No | No | No | No | No | Yes |
ReFS | No | No | Yes (from Windows Server 2012 and from Windows 8.1) | 部分的 - Only ReFS 1.x with Paragon ReFS for Linux | ? | ? | ? | ? | ? | ? | ? | ? |
ISO 9660 | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Rock Ridge | No | No | No | Yes | No | Yes | Yes | No | No | Yes | Yes | ? |
Joliet ("CDFS") | No | Yes | Yes | Yes | ? | Yes | Yes | Yes | Yes | ? | Yes | ? |
SquashFS | No | No | 部分的 (There are ports of unsquashfs and mksquashfs.) | Yes | No | 部分的 (There are ports of unsquashfs and mksquashfs.) | 部分的 (There are ports of unsquashfs and mksquashfs and fusefs-port.[86][87]) | No | No | No | No | No |
File system | DOS | Windows 9x | Windows NT | Linux | "classic" Mac OS | macOS | FreeBSD | OS/2 | BeOS | Minix | Solaris | z/OS |
関連項目
[編集]注釈
[編集]- ^ most permissive implementation
- ^ IBM introduced JFS with the initial release of AIX Version 3.1 in 1990. This file system now called JFS1. The new JFS, on which the Linux port was based, was first shipped in OS/2 Warp Server for e-Business in 1999. The same sourcebase was also used for release JFS2 on AIX 5L.
- ^ Microsoft first introduced FAT32 in MS-DOS 7.1 / Windows 95 OSR2 (OEM Service Release 2) and then later in Windows 98. NT-based Windows did not have any support for FAT32 up to Windows NT4; Windows 2000 was the first NT-based Windows OS that received the ability to work with it.
- ^ a b c d e These are the restrictions imposed by the on-disk directory entry structures themselves. Particular Installable File System drivers may place restrictions of their own on file and directory names; operating systems may also place restrictions of their own, across all filesystems. DOS, Windows, and OS/2 allow only the following characters from the current 8-bit OEM codepage in SFNs: A-Z, 0-9, characters ! # $ % & ' ( ) - @ ^ _ ` { } ~, as well as 0x80-0xFF and 0x20 (SPACE). Specifically, lowercase letters a-z, characters " * / : < > ? \ | + , . ; = [ ], control codes 0x00-0x1F, 0x7F and in some cases also 0xE5 are not allowed.) In LFNs, any UCS-2 Unicode except \ / : ? * " > < | and NUL are allowed in file and directory names across all filesystems. Unix-like systems disallow the characters / and NUL in file and directory names across all filesystems.
- ^ a b c d e For filesystems that have variable allocation unit (block/cluster) sizes, a range of size are given, indicating the maximum volume sizes for the minimum and the maximum possible allocation unit sizes of the filesystem (e.g. 512 bytes and 128 KiB for FAT — which is the cluster size range allowed by the on-disk data structures, although some Installable File System drivers and operating systems do not support cluster sizes larger than 32 KiB).
- ^ a b c d e f g h i j k l m n o p q r s t u v w x y z aa ab ac ad ae af ag ah ai aj ak In these filesystems the directory entries named "." and ".." have special status. Directory entries with these names are not prohibited, and indeed exist as normal directory entries in the on-disk data structures. However, they are mandatory directory entries, with mandatory values, that are automatically created in each directory when it is created; and directories without them are considered corrupt.
- ^ a b c d e f g h i j k l m n o p q r s t u v w x y z aa ab ac ad ae af ag ah ai aj ak al am The on-disk structures have no inherent limit. Particular Installable File System drivers and operating systems may impose limits of their own, however. Limited by its Current Directory Structure (CDS), DOS does not support more than 32 directory levels (except for DR DOS 3.31-6.0) or full pathnames longer than 66 バイト for FAT, or 255 characters for LFNs. Windows NT does not support full pathnames longer than 32,767 バイト for NTFS. Linux has a pathname limit of 4,096.
- ^ The file size in the inode is 1 8-bit byte followed by 1 16-bit word, for 24 bits. The actual maximum was 8,847,360 バイト, with 7 singly-indirect blocks and 1 doubly-indirect block; PWB/UNIX 1.0's variant had 8 singly-indirect blocks, making the maximum 524,288 バイト or half a MiB.
- ^ The actual maximum was 1,082,201,088 バイト, with 10 direct blocks, 1 singly-indirect block, 1 doubly-indirect block, and 1 triply-indirect block. The 4.0BSD and 4.1BSD versions, and the System V version, used 1,024-byte blocks rather than 512-byte blocks, making the maximum 4,311,812,608 バイト or approximately 4 GiB.
- ^ a b c d e f Depends on whether the FAT12, FAT16, and FAT32 implementation has support for LFNs. Where it does not, as in OS/2, DOS, Windows 95, Windows 98 in DOS-only mode and the Linux "msdos" driver, file names are limited to 8.3 format of 8-bit OEM characters (space padded in both the basename and extension parts) and may not contain NUL (end-of-directory marker) or character 5 (replacement for character 229 which itself is used as deleted-file marker). Short names also must not contain lowercase letters. A few special device names (CON, NUL, AUX, PRN, LPT1, COM1, etc.) should be avoided, as some operating systems (notably DOS, OS/2 and Windows) reserve them.
- ^ a b On-disk structures would support up to 4 GiB, but practical file size is limited by volume size.
- ^ While FAT32 partitions this large work fine once created, some software won't allow creation of FAT32 partitions larger than 32 GiB. This includes, notoriously, the Windows XP installation program and the Disk Management console in Windows 2000, XP, 2003 and Vista. Use FDISK from a Windows ME Emergency Boot Disk to avoid.[15]
- ^ The "." and ".." directory entries in HPFS that are seen by applications programs are a partial fiction created by the Installable File System drivers. The on-disk data structure for a directory does not contain entries by those names, but instead contains a special "start" entry. Whilst on-disk directory entries by those names are not physically prohibited, they cannot be created in normal operation, and a directory containing such entries is corrupt.
- ^ This is the limit of the on-disk structures. The HPFS Installable File System driver for OS/2 uses the top 5 bits of the volume sector number for its own use, limiting the volume size that it can handle to 64 GiB.
- ^ a b This is the limit of the on-disk structures. The NTFS driver for Windows NT limits the volume size that it can handle to 256 TiB and the file size to 16 TiB respectively.
- ^ The "classic" Mac OS provides two sets of functions to retrieve file names from an HFS Plus volume, one of them returning the full Unicode names, the other shortened names fitting in the older 31 byte limit to accommodate older applications.
- ^ HFS Plus mandates support for an escape sequence to allow arbitrary Unicode. Users of older software might see the escape sequences instead of the desired characters.
- ^ a b Depends on kernel version and arch. For 2.4 kernels the max is 2 TiB. For 32-bit 2.6 kernels it is 16 TiB. For 64-bit 2.6 kernels it is 8 EiB.
- ^ ReiserFS has a theoretical maximum file size of 1 EiB, but "page cache limits this to 8 Ti on architectures with 32 bit int"[28]
- ^ Note that the filename can be much longer XFS#Extended attributes
- ^ a b XFS has a limitation under Linux 2.4 of 64 TiB file size, but Linux 2.4 only supports a maximum block size of 2 TiB. This limitation is not present under IRIX.
- ^ a b QFS allows files to exceed the size of disk when used with its integrated HSM, as only part of the file need reside on disk at any one time.
- ^ Varies wildly according to block size and fragmentation of block allocation groups.
- ^ a b NSS allows files to have multiple names, in separate namespaces.
- ^ Some namespaces had lower name length limits. "LONG" had an 80-byte limit, "NWFS" 80 バイト, "NFS" 40 バイト and "DOS" imposed 8.3 filename.
- ^ Maximum combined filename/filetype length is 236 バイト; each component has an individual maximum length of 255 バイト.
- ^ Maximum pathname length is 4,096 バイト, but quoted limits on individual components add up to 1,664 バイト.
- ^ This restriction might be lifted in newer versions.
- ^ a b Sparse files can be larger than the file system size, even though they can't contain more data.
- ^ a b Maximum file size on a VMFS volume depends on the block size for that VMFS volume. The figures here are obtained by using the maximum block size.
- ^ ISO 9660#Restrictions
- ^ Through the use of multi-extents, a file can consist of multiple segments, each up to 4 GiB in size. See ISO 9660#The 2 GiB .28or 4 GiB depending on implementation.29 file size limit
- ^ Assuming the typical 2048 Byte sector size. The volume size is specified as a 32 bit value identifying the number of sectors on the volume.
- ^ Implemented in later versions as an extension
- ^ Some FAT implementations, such as in Linux, show file modification timestamp (mtime) in the metadata change timestamp (ctime) field. This timestamp is however, not updated on file metadata change.
- ^ Particular Installable File System drivers and operating systems may not support extended attributes on FAT12 and FAT16. The OS/2 and Windows NT filesystem drivers for FAT12 and FAT16 support extended attributes (using a "EA DATA. SF" pseudo-file to reserve the clusters allocated to them). Other filesystem drivers for other operating systems do not.
- ^ The f-node contains a field for a user identifier. This is not used except by OS/2 Warp Server, however.
- ^ NTFS access control lists can express any access policy possible using simple POSIX file permissions (and far more), but use of a POSIX-like interface is not supported without an add-on such as Services for UNIX or Cygwin.
- ^ As of Vista, NTFS has support for Mandatory Labels, which are used to enforce Mandatory Integrity Control.[34]
- ^ Initially, ReFS lacked support for ADS, but Server 2012 R2 and up add support for ADS on ReFS
- ^ Data checksums not enabled by default
- ^ a b c d Access-control lists and MAC labels are layered on top of extended attributes.
- ^ Some operating systems implemented extended attributes as a layer over UFS1 with a parallel backing file (e.g., FreeBSD 4.x).
- ^ a b c d e f g h i j k l m n Some Installable File System drivers and operating systems may not support extended attributes, access control lists or security labels on these filesystems. Linux kernels prior to 2.6.x may either be missing support for these altogether or require a patch.
- ^ Journal and metadata only[35]
- ^ Creation time stored since June 2015, xfsprogs version 3.2.3
- ^ Metadata checksums stored since June 2015, xfsprogs version 3.2.3
- ^ a b c d e f The local time, timezone/UTC offset, and date are derived from the time settings of the reference/single timesync source in the NDS tree.
- ^ a b Novell calls this feature "multiple data streams". Published specifications say that NWFS allows for 16 attributes and 10 data streams, and NSS allows for unlimited quantities of both.
- ^ a b Some file and directory metadata is stored on the NetWare server irrespective of whether Directory Services is installed or not, like date/time of creation, file size, purge status, etc; and some file and directory metadata is stored in NDS/eDirectory, like file/object permissions, ownership, etc.
- ^ Record Management Services (RMS) attributes include record type and size, among many others.
- ^ File permission in 9P are a variation of the traditional Unix permissions with some minor changes, e.g. the suid bit is replaced by a new 'exclusive access' bit.
- ^ MAC/Sensitivity labels in the file system are not out of the question as a future compatible change but aren't part of any available version of ZFS.
- ^ Solaris "extended attributes" are really full-blown alternate data streams, in both the Solaris UFS and ZFS.
- ^ disabling copy-on-write (COW) to prevent fragmentation also disables checksumming
- ^ Access times are preserved from the original file system at creation time, but Rock Ridge file systems themselves are read-only.
- ^ libburnia can backup and restore ACLs with file system creation and extraction programs, but no kernel support exists.
- ^ a b libburnia can backup and restore extended attributes and MAC labels with file system creation and extraction programs, but no kernel support exists.
- ^ System V Release 4, and some other Unix systems, retrofitted symbolic links to their versions of the Version 7 Unix file system, although the original version didn't support them.
- ^ Context based symlinks were supported in GFS, GFS2 only supports standard symlinks since the bind mount feature of the Linux VFS has made context based symlinks obsolete
- ^ Optional journaling of data
- ^ As of Windows Vista, NTFS fully supports symbolic links.[38] NTFS 3.0 (Windows 2000) and higher can create junctions, which allow entire directories (but not individual files) to be mapped to elsewhere in the directory tree of the same partition (file system). These are implemented through reparse points, which allow the normal process of filename resolution to be extended in a flexible manner.
- ^ a b NTFS stores everything, even the file data, as meta-data, so its log is closer to block journaling.
- ^ a b While NTFS itself supports case sensitivity, the Win32 environment subsystem cannot create files whose names differ only by case for compatibility reasons. When a file is opened for writing, if there is any existing file whose name is a case-insensitive match for the new file, the existing file is truncated and opened for writing instead of a new file with a different name being created. Other subsystems like e. g. Services for Unix, that operate directly above the kernel and not on top of Win32 can have case-sensitivity.
- ^ NTFS does not internally support snapshots, but in conjunction with the Volume Shadow Copy Service can maintain persistent block differential volume snapshots.
- ^ Supported only on Windows Server SKUs. However, partitions deduplicated on Server can be used on Client.
- ^ Metadata-only journaling was introduced in the Mac OS X 10.2.2 HFS Plus driver; journaling is enabled by default on Mac OS X 10.3 and later.
- ^ Although often believed to be case sensitive, HFS Plus normally is not. The typical default installation is case-preserving only. From Mac OS X 10.3 on the command newfs_hfs -s will create a case-sensitive new file system.[41] HFS Plus version 5 optionally supports case-sensitivity. However, since case-sensitivity is fundamentally different from case-insensitivity, a new signature was required so existing HFS Plus utilities would not see case-sensitivity as a file system error that needed to be corrected. Since the new signature is 'HX', it is often believed this is a new filesystem instead of a simply an upgraded version of HFS Plus.[42][43]
- ^ Mac OS X Tiger (10.4) and late versions of Panther (10.3) provide file change logging (it's a feature of the file system software, not of the volume format, actually).[44]
- ^ HFS+ does not actually encrypt files: to implement FileVault, OS X creates an HFS+ filesystem in a sparse, encrypted disk image that is automatically mounted over the home directory when the user logs in.
- ^ "Soft dependencies" (softdep) in NetBSD, called "soft updates" in FreeBSD provide meta-data consistency at all times without double writes (journaling)
- ^ a b c d e UDF, LFS, and NILFS are log-structured file systems and behave as if the entire file system were a journal.
- ^ Linux kernel versions 2.6.12 and newer.
- ^ a b c Off by default.
- ^ Full block journaling for ReiserFS was added to Linux 2.6.8.
- ^ a b Reiser4 supports transparent compression and encryption with the cryptcompress plugin which is the default file handler in version 4.1.
- ^ Optionally no on IRIX.
- ^ Particular Installable File System drivers and operating systems may not support case sensitivity for JFS. OS/2 does not, and Linux has a mount option for disabling case sensitivity.
- ^ a b c d Case-sensitivity/Preservation depends on client. Windows, DOS, and OS/2 clients don't see/keep case differences, whereas clients accessing via NFS or AFP may.
- ^ a b The file change logs, last entry change timestamps, and other filesystem metadata, are all part of the extensive suite of auditing capabilities built into NDS/eDirectory called NSure Audit.[48]
- ^ a b Available only in the "NFS" namespace.
- ^ a b These are referred to as "aliases".
- ^ VxFS provides an optional feature called "Storage Checkpoints" which allows for advanced file system snapshots.
- ^ a b ZFS is a transactional filesystem using copy-on-write semantics, guaranteeing an always-consistent on-disk state without the use of a traditional journal. However, it does also implement an intent log to provide better performance when synchronous writes are requested.
- ^ Applies only to proprietary ZFS release and ZFS On Linux. Encryption support is not yet available in whole OpenZFS.[49][50]
- ^ a b c Some file system creation implementations reuse block references and support deduplication this way. This is not supported by the standard, but usually works well due to the file system's read-only nature.
- ^ a b Variable block size refers to systems which support different block sizes on a per-file basis. (This is similar to extents but a slightly different implementational choice.) The current implementation in UFS2 is read-only.
- ^ a b SuperStor in DR DOS 6.0, PalmDOS 1.0, PC DOS 6.1 and 6.3, Stacker in Novell DOS 7, OpenDOS 7.01, DR-DOS 7.02 (and higher), and PC DOS 7.0 (and higher), DoubleSpace in MS-DOS 6.0 and 6.20, and DriveSpace in MS-DOS 6.22 and Windows 95, 98 and Me are disk compression schemes for FAT, but are not supported for other operating systems.
- ^ Only for "stuffed" inodes
- ^ a b c d Other block:fragment size ratios supported; 8:1 is typical and recommended by most implementations.
- ^ e2compr, a set of patches providing block-based compression for ext2, has been available since 1997, but has never been merged into the mainline Linux kernel.
- ^ a b c Fragments were planned, but never actually implemented on ext2 and ext3.
- ^ Stores one largest extent in disk, and caches multiple extents in DRAM dynamically.
- ^ a b Tail packing is technically a special case of block suballocation where the suballocation unit size is always 1 byte.
- ^ In "extents" mode.
- ^ Each possible size (in sectors) of file tail has a corresponding suballocation block chain in which all the tails of that size are stored. The overhead of managing suballocation block chains is usually less than the amount of block overhead saved by being able to increase the block size but the process is less efficient if there is not much free disk space.
- ^ Depends on UDF implementation.
- ^ a b c Linux supports the zisofs extension that allows per-file compression, and file system creation tools may support creating such images. zisofs images are incompatible on non-Linux OSes.
- ^ a b c ISO 9660 Level 3 only
- ^ Supported using only EVMS; not currently supported using LVM
- ^ a b c d Provided in Plan 9 from User Space
出典
[編集]- ^ “In His Own Words: Gary Kildall”. Remarkable People. Computer History Museum (2016年8月2日). Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ Computer Connections: People, Places, and Events in the Evolution of the Personal Computer Industry. Kildall Family. (2016-08-02) 2016年11月17日閲覧。.
- ^ “Extensions to MS-DOS Run CD-ROM”. InfoWorld 8 (38): 1, 8. (1986-09-22) 2016年11月9日閲覧。.
- ^ “Polycenter File System - - HELP” (20 October 1993). 9 March 2012時点のオリジナルよりアーカイブ。 Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ "Sun Microsystems Expands High Performance Computing Portfolio with Definitive Agreement to Acquire Assets of Cluster File Systems, Including the Lustre File System" (Press release). Santa Clara, Calif.: Sun Microsystems, Inc. 12 September 2007. 2007年10月2日時点のオリジナルよりアーカイブ。
- ^ “hammer license” (2017年9月27日). Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ tfs: Next Generation File System, Redox OS, (2017-10-28) 2017年10月29日閲覧。
- ^ “This Year in Redox - Redox - Your Next(Gen) OS” (英語). www.redox-os.org. 2017年10月29日閲覧。
- ^ “Rust-Based Redox OS Had A Busy Year With Rewriting Its Kernel, Writing A File-System - Phoronix” (英語). www.phoronix.com. 2017年10月29日閲覧。
- ^ “TFS File-System Still Aiming To Compete With ZFS, Written In Rust - Phoronix” (英語). phoronix.com. 2017年10月29日閲覧。
- ^ “Contributors to redox-os/tfs · GitHub”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ redox: Redox: A Rust Operating System, Redox OS, (2017-10-28) 2017年10月29日閲覧。
- ^ “SFS file system”. IBM Knowledge Center. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ a b c d “File System Functionality Comparison”. Microsoft Developer Network. Microsoft. 4 November 2017閲覧。
- ^ “Limitations of the FAT32 File System in Windows XP”. Microsoft. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “GEMDOS Overview”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/APFS_Guide/FAQ/FAQ.html
- ^ https://developer.apple.com/library/archive/documentation/FileManagement/Conceptual/APFS_Guide/VolumeFormatComparison/VolumeFormatComparison.html
- ^ http://dubeyko.com/development/FileSystems/NTFS/ntfsdoc.pdf
- ^ a b c d Steven Sinofsky (January 16, 2012). “Building the next generation file system for Windows: ReFS”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Resilient File System (ReFS) overview” (英語). docs.microsoft.com. 2017年11月7日閲覧。
- ^ “Mac OS X: Mac OS Extended format (HFS Plus) volume and file limits”. support.apple.com (July 26, 2016). Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Mac OS 8, 9: Mac OS Extended Format - Volume and File Limits”. support.apple.com (February 20, 2012). Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ Matthew Dillon. “HAMMER2 Design Document”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ Matthew Dillon (June 21, 2008). “The HAMMER Filesystem”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Frequently Asked Questions for FreeBSD 9.X and 10.X”. FreeBSD Documentation Project. 2016年3月20日閲覧。 “If there was not a fsck(8) memory limit the maximum filesystem size would be 2 ^ 64 (blocks) * 32 KB => 16 Exa * 32 KB => 512 Zettaバイト.”
- ^ “Interviews/EricSandeen”. Fedora Project Wiki (9 June 2008). Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “FAQ”. namesys (15 October 2003). 19 July 2006時点のオリジナルよりアーカイブ。 Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Joliet Specification” (22 May 1995). 14 April 2009時点のオリジナルよりアーカイブ。 Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “RT–11 Volume and File Formats Manual”. Digital Equipment Corporation. p. 1-26 .. 1-32 (August 1991). Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “RT–11 Volume and File Formats Manual”. Digital Equipment Corporation. p. 1-4 .. 1-12 (August 1991). Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Format of the Unix 6 file system”. 2016年2月21日閲覧。
- ^ See dinode structure on page 355 (FILESYS(5)) of “Unix Programmers Manual”. Murray Hill, New Jersey: Bell Telephone Laboratories (January 1979). 2016年2月21日閲覧。
- ^ “Mandatory Integrity Control”. Microsoft Developer Network. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Ext4 Metadata Checksums - Ext4” (英語). ext4.wiki.kernel.org. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Mac users, meet APFS: macOS's new file system - ZDNet”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Apple File System Guide - FAQ”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ Mark Russinovich (February 2007). “Windows Administration: Inside the Windows Vista Kernel: Part 1”. TechNet .
- ^ “About Data Deduplication”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Mac OS X 10.7 Lion: the Ars Technica review”. Ars Technica. 14 December 2017閲覧。 “To keep track of hard links, HFS+ creates a separate file for each hard link inside a hidden directory at the root level of the volume.”
- ^
newfs_hfs(8)
– Darwin and macOS System Manager's Manual - ^ “File System Comparisons”. Apple. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。 (hasn't been updated to discuss HFSX)
- ^ “Technical Note TN1150: HFS Plus Volume Format”. Apple. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。 (Very technical overview of HFS Plus and HFSX.)
- ^ fslogger
- ^ “Ext4 encryption”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “F2FS encryption”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “XFS, Reflinks and Deduplication”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ Filesystem Events tracked by NSure
- ^ “How to Manage ZFS Data Encryption”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ https://github.com/zfsonlinux/zfs/pull/5769
- ^ “Btrfs FAQ”. Btrfs Wiki. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “GitHub - redox-os/tfs: Next Generation File System” (英語). GitHub. 2017年11月14日閲覧。
- ^ “Add ATA trim support, trim sectors which are no longer used. · redox-os/tfs@bce6ea1” (英語). GitHub. 2017年11月14日閲覧。
- ^ “Just Enough Operating System (JeOS): Technical Information | SUSE” (英語). www.suse.com. 28 April 2018閲覧。
- ^ a b c
resize2fs(8)
– JM Project Linux Administration and Privileged Commands マニュアル - ^ a b c d e f PartitionMagic
- ^ https://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-tools.git/
- ^ “IBM's Journaled File System (JFS) for Linux”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Frequently Asked Questions (Old Wiki)”. 5 May 2018閲覧。
- ^ “nilfs-resize(8)”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “ntfsresize(8)”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Resize reiserfs”. Reiserfs wiki. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Resizing File Systems”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Growing an XFS File System”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Resizing and Growing Disks”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ a b “DMSDOS CVF module” (1998年11月19日). 2016年11月2日時点のオリジナルよりアーカイブ。2016年11月1日閲覧。 “Usually all data for one cluster are stored in contiguous sectors, but if the filesystem is too fragmented there may not be a 'free hole' that is large enough for the data. […] Drivespace 3 and Stacker know a hack for that situation: they allow storing the data of one cluster in several fragments on the disk.”
- ^ a b “Mapping DOS FAT to MDFAT”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ a b “CVF Region: MDFAT”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “XFS Adds Shared Data Extents For Linux 4.9”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “AIX documentation: JFS data compression”. IBM. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ a b “Paragon HFS+ for Windows 10”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Porting an Ancient Filesystem to Modern Linux”. Time To Pull The Plug. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “A port of the xiafs filesystem to modern Linux kernels.”. Github (cdtk). Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ a b c “Paragon ExtFS for Windows”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ a b c “FAQ”. Ext2 Installable File System For Windows. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。 (Provides kernel level read/write access to Ext2 and Ext3 volumes in Windows NT4, 2000, XP and Vista.)
- ^ a b c “Ext2Fsd Project: Open source ext3/4 file system driver for Windows (2K/XP/WIN7/WIN8)”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ a b c “Paragon ExtFS for Mac”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ a b “FreeBSD Handbook”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ a b “Debian GNU/kFreeBSD”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Lustre Wiki”. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “About Shared File Systems and the Linux Client - Sun QFS and Sun Storage Archive Manager 5.3 Installation Guide”. 2016年3月14日閲覧。
- ^ “ZFS Filesystem for FUSE/Linux”. Wizy Wiki (30 November 2009). 13 May 2013時点のオリジナルよりアーカイブ。 Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “ZFS on Linux”. Lawrence Livermore National Laboratory. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “Apple Seeds ZFS Read/Write Developer Preview 1.1 for Leopard”. Mac Rumors (4 October 2007). Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “WinBtrfs”. Github (maharmstone). Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “squashfs-tools”. Freshports. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
- ^ “fusefs-squashfuse”. Freshports. Template:Cite webの呼び出しエラー:引数 accessdate は必須です。
外部リンク
[編集]- A speed comparison of filesystems on Linux 2.4.5 (archived)
- Filesystems (ext3, reiser, xfs, jfs) comparison on Debian Etch (April 23, 2006)
- Block allocation strategies of various filesystems
- What are the (dis)advantages of ext4, ReiserFS, JFS, and XFS? - Unix & Linux Stack Exchange