Ext4: Difference between revisions

Jump to navigation Jump to search
1,217 bytes added ,  3 years ago
Add required features.
[unchecked revision][unchecked revision]
m (Fix formatting.)
(Add required features.)
Line 241:
|-
| 1020 || 1023 || 4 || Checksum of the superblock.
|}
 
Required Features:
 
{| {{wikitable}}
! Flag
Value
! Description
|-
| 0x0001 || Compression is used.
|-
| 0x00002 || Directory entries contain a type field.
|-
| 0x00004 || Filesystem needs to replay the Journal to recover data.
|-
| 0x00008 || Filesystem uses a journal device.
|-
| 0x00010 || Filesystem uses Meta Block Groups.
|-
| 0x00040 || Filesystem uses extents for files.
|-
| 0x00080 || Filesystem uses 64 bit features.
|-
| 0x00100 || Filesystem uses Multiple Mount Protection.
|-
| 0x00200 || Filesystem uses Flex Block Groups.
|-
| 0x00400 || Filesystem uses Extended Attributes in Inodes.
|-
| 0x01000 || Filesystem uses Data in Directory Entries. This is not implemented as of Linux 5.9rc3.
|-
| 0x02000 || Filesystem stores the metadata checksum seed in the superblock. This allows for changing the UUID wihtout rewriting all of the metadata blocks.
|-
| 0x04000 || Directories may be larger than 4GiB and have a maximum HTREE depth of 3.
|-
| 0x08000 || Data may be stored in the inode. See [[Ext4#Inline_Data|Inline Data]] for an discussion of this feature.
|-
| 0x10000 || Filesystem uses Encryption.
|-
| 0x20000 || Filesystem uses case folding, storing the filesystem-wide encoding in inodes.
|}
 
Anonymous user
Cookies help us deliver our services. By using our services, you agree to our use of cookies.

Navigation menu