Difference between revisions of "Ext4"

From ArchWiki
Jump to navigation Jump to search
m (style)
m (Enabling metadata checksums: typo)
(One intermediate revision by the same user not shown)
Line 272: Line 272:
== Enabling metadata checksums ==
== Enabling metadata checksums ==
{{Out of date|{{ic|metadata_csum}} seems to be enabled by default for new file systems since {{Pkg|e2fsprogs}} 1.44, see {{ic|/etc/mke2fs.conf}}.}}
If the CPU supports SSE 4.2, make sure the {{ic|crc32c_intel}} kernel module is loaded in order to enable the hardware accelerated CRC32C algorithm [https://ext4.wiki.kernel.org/index.php/Ext4_Metadata_Checksums#Benchmarking]. If not, load the {{Ic|crc32c_generic}} module instead.
If the CPU supports SSE 4.2, make sure the {{ic|crc32c_intel}} kernel module is loaded in order to enable the hardware accelerated CRC32C algorithm [https://ext4.wiki.kernel.org/index.php/Ext4_Metadata_Checksums#Benchmarking]. If not, load the {{Ic|crc32c_generic}} module instead.

Revision as of 11:15, 22 October 2018

From Ext4 - Linux Kernel Newbies:

Ext4 is the evolution of the most used Linux filesystem, Ext3. In many ways, Ext4 is a deeper improvement over Ext3 than Ext3 was over Ext2. Ext3 was mostly about adding journaling to Ext2, but Ext4 modifies important data structures of the filesystem such as the ones destined to store the file data. The result is a filesystem with an improved design, better performance, reliability, and features.

Create a new ext4 filesystem

To format a partition do:

# mkfs.ext4 /dev/partition
  • See mke2fs(8) for more options; edit /etc/mke2fs.conf to view/configure default options.
  • If supported, you may want to enable metadata checksums.

Bytes-per-inode ratio

From mke2fs(8):

mke2fs creates an inode for every bytes-per-inode bytes of space on the disk. The larger the bytes-per-inode ratio, the fewer inodes will be created.

Creating a new file, directory, symlink etc. requires at least one free inode. If the inode count is too low, no file can be created on the filesystem even though there is still space left on it.

Because it is not possible to change either the bytes-per-inode ratio or the inode count after the filesystem is created, mkfs.ext4 uses by default a rather low ratio of one inode every 16384 bytes (16 KiB) to avoid this situation.

However, for partitions with size in the hundreds or thousands of GB and average file size in the megabyte range, this usually results in a much too large inode number because the number of files created never reaches the number of inodes.

This results in a waste of disk space, because all those unused inodes each take up 256 bytes on the filesystem (this is also set in /etc/mke2fs.conf but should not be changed). 256 * several millions = quite a few gigabytes wasted in unused inodes.

This situation can be evaluated by comparing the {I}Use% figures provided by df and df -i:

$ df -h /home
Filesystem              Size    Used   Avail  Use%   Mounted on
/dev/mapper/lvm-home    115G    56G    59G    49%    /home
$ df -hi /home
Filesystem              Inodes  IUsed  IFree  IUse%  Mounted on
/dev/mapper/lvm-home    1.8M    1.1K   1.8M   1%     /home

To specify a different bytes-per-inode ratio, you can use the -T usage-type option which hints at the expected usage of the filesystem using types defined in /etc/mke2fs.conf. Among those types are the bigger largefile and largefile4 which offer more relevant ratios of one inode every 1 MiB and 4 MiB respectively. It can be used as such:

# mkfs.ext4 -T largefile /dev/device

The bytes-per-inode ratio can also be set directly via the -i option: e.g. use -i 2097152 for a 2 MiB ratio and -i 6291456 for a 6 MiB ratio.

Tip: Conversely, if you are setting up a partition dedicated to host millions of small files like emails or newsgroup items, you can use smaller usage-type values such as news (one inode for every 4096 bytes) or small (same plus smaller inode and block sizes).
Warning: If you make a heavy use of symbolic links, make sure to keep the inode count high enough with a low bytes-per-inode ratio, because while not taking more space every new symbolic link consumes one new inode and therefore the filesystem may run out of them quickly.

Reserved blocks

By default, 5% of the filesystem blocks will be reserved for the super-user, to avoid fragmentation and "allow root-owned daemons to continue to function correctly after non-privileged processes are prevented from writing to the filesystem" (from mke2fs(8)).

For modern high-capacity disks, this is higher than necessary if the partition is used as a long-term archive or not crucial to system operations (like /home). See this email for the opinion of ext4 developer Ted Ts'o on reserved blocks.

It is generally safe to reduce the percentage of reserved blocks to free up disk space when the partition is either:

  • Very large (for example > 50G)
  • Used as long-term archive, i.e., where files will not be deleted and created very often

The -m option of ext4-related utilities allows to specify the percentage of reserved blocks.

To totally prevent reserving blocks upon filesystem creation, use:

# mkfs.ext4 -m 0 /dev/device

To reduce it to 1% afterwards, use:

# tune2fs -m 1 /dev/device

You can use findmnt(8) to find the device name:

$ findmnt /the/mount/point

Migrating from ext2/ext3 to ext4

Mounting ext2/ext3 partitions as ext4 without converting


A compromise between fully converting to ext4 and simply remaining with ext2/ext3 is to mount the partitions as ext4.


  • Compatibility (the filesystem can continue to be mounted as ext3) – This allows users to still read the filesystem from other operating systems without ext4 support (e.g. Windows with ext2/ext3 drivers)
  • Improved performance (though not as much as a fully-converted ext4 partition).[1] [2]


  • Fewer features of ext4 are used (only those that do not change the disk format such as multiblock allocation and delayed allocation)
Note: Except for the relative novelty of ext4 (which can be seen as a risk), there is no major drawback to this technique.


  1. Edit /etc/fstab and change the 'type' from ext2/ext3 to ext4 for any partitions you would like to mount as ext4.
  2. Re-mount the affected partitions.

Converting ext2/ext3 partitions to ext4


To experience the benefits of ext4, an irreversible conversion process must be completed.


  • Improved performance and new features.[3] [4]


  • Partitions that contain mostly static files, such as a /boot partition, may not benefit from the new features. Also, adding a journal (which is implied by moving a ext2 partition to ext3/4) always incurs performance overhead.
  • Irreversible (ext4 partitions cannot be 'downgraded' to ext2/ext3. It is, however, backwards compatible until extent and other unique options are enabled)


These instructions were adapted from Kernel documentation and an BBS thread.

  • If you convert the system's root filesystem, ensure that the 'fallback' initramfs is available at reboot. Alternatively, add ext4 according to Mkinitcpio#MODULES and regenerate the initramfs before starting.
  • If you decide to convert a separate /boot partition, ensure the bootloader supports booting from ext4.

In the following steps /dev/sdxX denotes the path to the partition to be converted, such as /dev/sda1.

  1. BACK-UP! Back-up all data on any ext3 partitions that are to be converted to ext4. A useful package, especially for root partitions, is Clonezilla.
  2. Edit /etc/fstab and change the 'type' from ext3 to ext4 for any partitions that are to be converted to ext4.
  3. Boot the live medium (if necessary). The conversion process with e2fsprogs must be done when the drive is not mounted. If converting a root partition, the simplest way to achieve this is to boot from some other live medium.
  4. Ensure the partition is NOT mounted
  5. If you want to convert a ext2 partition, the first conversion step is to add a journal by running tune2fs -j /dev/sdxX as root; making it a ext3 partition.
  6. Run tune2fs -O extent,uninit_bg,dir_index /dev/sdxX as root. This command converts the ext3 filesystem to ext4 (irreversibly).
  7. Run fsck -f /dev/sdxX as root.
    • The user must fsck the filesystem, or it will be unreadable! This fsck run is needed to return the filesystem to a consistent state. It will find checksum errors in the group descriptors - this is expected. The -f option asks fsck to force checking even if the file system seems clean. The -p option may be used on top to 'automatically repair' (otherwise, the user will be asked for input for each error).
  8. Recommended: mount the partition and run e4defrag -c -v /dev/sdxX as root.
    • Even though the filesystem is now converted to ext4, all files that have been written before the conversion do not yet take advantage of the extent option of ext4, which will improve large file performance and reduce fragmentation and filesystem check time. In order to fully take advantage of ext4, all files would have to be rewritten on disk. Use e4defrag to take care of this problem.
  9. Reboot Arch Linux!

Using file-based encryption

Note: Ext4 forbids encrypting the root (/) directory and will produce an error on kernel 4.13 and later [5] [6].

ext4 supports file-based encryption. In a directory tree marked for encryption, file contents, filenames, and symbolic link targets are all encrypted. Encryption keys are stored in the kernel keyring. See also Quarkslab's blog entry with a write-up of the feature, an overview of the implementation state, and practical test results with kernel 4.1.

The encryption relies on the kernel option CONFIG_EXT4_ENCRYPTION, which is enabled by default, as well as the e4crypt command from the e2fsprogs package.

A precondition is that your filesystem is using a supported block size for encryption:

# tune2fs -l /dev/device | grep 'Block size'
Block size:               4096
# getconf PAGE_SIZE

If these values are not the same, then your filesystem will not support encryption, so do not proceed further.

  • Once the encryption feature flag is enabled, kernels older than 4.1 will be unable to mount the filesystem.
  • If the /boot/ directory is on the ext4 file system, check that the boot loader supports the ext4 encryption.

Next, enable the encryption feature flag on your filesystem:

# tune2fs -O encrypt /dev/device
Tip: The operation can be reverted with debugfs -w -R "feature -encrypt" /dev/device. Run fsck before and after to ensure the integrity of the file system.

Next, make a directory to encrypt:

# mkdir /encrypted

Note that encryption can only be applied to an empty directory. New files and subdirectories within an encrypted directory inherit its encryption policy. Encrypting already existing files is not yet supported.

Now generate and add a new key to your keyring. This step must be repeated every time you flush your keyring (i.e., reboot):

# e4crypt add_key
Enter passphrase (echo disabled): 
Added key with descriptor [f88747555a6115f5]
Warning: If you forget your passphrase, there will be no way to decrypt your files. It also is not yet possible to change a passphrase after it has been set.
Note: To help prevent dictionary attacks on your passphrase, a random salt is automatically generated and stored in the ext4 filesystem superblock. Both the passphrase and the salt are used to derive the actual encryption key. As a consequence of this, if you have multiple ext4 filesystems with encryption enabled mounted, then e4crypt add_key will actually add multiple keys, one per filesystem. Although any key can be used on any filesystem, it would be wise to only use, on a given filesystem, keys using that filesystem's salt. Otherwise, you risk being unable to decrypt files on filesystem A if filesystem B is unmounted. Alternatively, you can use the -S option to e4crypt add_key to specify a salt yourself.

Now you know the descriptor for your key. Make sure the key is in your session keyring:

# keyctl show
Session Keyring
1021618178 --alswrv   1000  1000  keyring: _ses
 176349519 --alsw-v   1000  1000   \_ logon: ext4:f88747555a6115f5

Almost done. Now set an encryption policy on the directory (assign the key to it):

# e4crypt set_policy f88747555a6115f5 /encrypted

This completes setting up encryption for a directory named /encrypted. If you try accessing the directory without adding the key into your keyring, filenames and their contents will be seen as encrypted gibberish.

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: "Some applications" is fuzzy. A reference about such error? (Discuss in Talk:Ext4#)
  • Some applications cannot open files in directories encrypted using this method. Try moving the file outside of the encrypted directory before assuming it is broken. In this case, you will often see a message about a missing key.
  • Logging in does automatically unlock home directories encrypted by this method when using GDM or console login.
Note: For security reasons, unencrypted files are not allowed to exist in an encrypted directory. As such, attempting to move (mv) unencrypted files into an encrypted directory will
  • fail, if both directories are on the same filesystem mount point. This happens because mv will only update the directory index to point to the new directory, but not the file's data inodes (which contain the crypto reference).
  • succeed, if both directories are on different filesystem mount points (new data inodes are created).

In both cases it is better to copy (cp) files instead, because that leaves the option to securely delete the unencrypted original with shred or a similar tool.

Improving performance


E4rat is a preload application designed for the ext4 filesystem. It monitors files opened during boot, optimizes their placement on the partition to improve access time, and preloads them at the very beginning of the boot process. E4rat does not offer improvements with SSDs, whose access time is negligible compared to hard disks.

Disabling access time update

The ext4 file system records information about when a file was last accessed and there is a cost associated with recording it. With the noatime option, the access timestamps on the filesystem are not updated.

/dev/sda5    /    ext4    defaults,noatime    0    1

Increasing commit interval

The sync interval for data and metadata can be increased by providing a higher time delay to the commit option.

The default 5 sec means that if the power is lost, one will lose as much as the latest 5 seconds of work. It forces a full sync of all data/journal to physical media every 5 seconds. The filesystem will not be damaged though, thanks to the journaling. The following fstab illustrates the use of commit:

/dev/sda5    /    ext4    defaults,noatime,commit=60    0    1

Turning barriers off

Warning: Disabling barriers for disks without battery-backed cache is not recommended and can lead to severe file system corruption and data loss.

Ext4 enables write barriers by default. It ensures that file system metadata is correctly written and ordered on disk, even when write caches lose power. This goes with a performance cost especially for applications that use fsync heavily or create and delete many small files. For disks that have a write cache that is battery-backed in one way or another, disabling barriers may safely improve performance.

To turn barriers off, add the option barrier=0 to the desired filesystem. For example:

/dev/sda5    /    ext4    noatime,barrier=0    0    1

Disabling journaling

Warning: Using a filesystem without journaling can result in data loss in case of sudden dismount like power failure or kernel lockup.

Disabling the journal with ext4 can be done with the following command on an unmounted disk:

# tune2fs -O "^has_journal" /dev/sdXN

Enabling metadata checksums

Tango-view-refresh-red.pngThis article or section is out of date.Tango-view-refresh-red.png

Reason: metadata_csum seems to be enabled by default for new file systems since e2fsprogs 1.44, see /etc/mke2fs.conf. (Discuss in Talk:Ext4#)

If the CPU supports SSE 4.2, make sure the crc32c_intel kernel module is loaded in order to enable the hardware accelerated CRC32C algorithm [7]. If not, load the crc32c_generic module instead.

To read more about metadata checksums, see the ext4 wiki.

  • In both cases the file system must not be mounted.
  • Metadata checksums is supported on e2fsprogs 1.43 and later.
  • Use dump2fs to check if features were successfully enabled:
# dumpe2fs -h /dev/path/to/disk

New filesystem

To enable support for ext4 metadata checksums on creating a new file system:

# mkfs.ext4 -O metadata_csum /dev/path/to/disk

Convert existing filesystem

First the partition needs to be checked and optimized using e2fsck:

# e2fsck -Df /dev/path/to/disk  

Convert the filesystem to 64bit:

# resize2fs -b /dev/path/to/disk 

Finally enable checksums support:

# tune2fs -O metadata_csum /dev/path/to/disk

See also