|Developer(s)||Mingming Cao, Andreas Dilger, Alex Zhuravlev (Tomas), Dave Kleikamp, Theodore Ts'o, Eric Sandeen, Sam Naghshineh, others|
|Full name||Fourth extended file system|
|Partition identifier||0x83: MBR / EBR.|
3B8F8425-20E0-4F3B-907F-1A25A76F98E8: GPT /srv (server data) partition.
|Directory contents||Linked list, hashed B-tree|
|File allocation||Extents / Bitmap|
|Max. volume size||1 EiB (for 4 KiB block size)|
|Max. file size||16 TiB (for 4 KiB block size)|
|Max. number of files||4 billion (specified at filesystem creation time)|
|Max. filename length||255 bytes|
|Allowed characters in filenames||All bytes except NUL ('\0') and '/' and the special file names "." and ".." which are not forbidden but are always used for a respective special purpose.|
|Dates recorded||modification (mtime), attribute modification (ctime), access (atime), delete (dtime), create (crtime)|
|Date range||14 December 1901 - 10 May 2446|
|Attributes||acl, bh, bsddf, commit=nrsec, data=journal, data=ordered, data=writeback, delalloc, extents, journal_dev, mballoc, minixdf, noacl, nobh, nodelalloc, noextents, nomballoc, nombcache, nouser_xattr, oldalloc, orlov, user_xattr|
|File system permissions||POSIX, POSIX ACLs|
|Supported operating systems|
ext4 was initially a series of backward-compatible extensions to ext3, many of them originally developed by Cluster File Systems for the Lustre file system between 2003 and 2006, meant to extend storage limits and add other performance improvements. However, other Linux kernel developers opposed accepting extensions to ext3 for stability reasons, and proposed to fork the source code of ext3, rename it as ext4, and perform all the development there, without affecting the current ext3 users. This proposal was accepted, and on 28 June 2006, Theodore Ts'o, the ext3 maintainer, announced the new plan of development for ext4.
A preliminary development version of ext4 was included in version 2.6.19 of the Linux kernel. On 11 October 2008, the patches that mark ext4 as stable code were merged in the Linux 2.6.28 source code repositories, denoting the end of the development phase and recommending ext4 adoption. Kernel 2.6.28, containing the ext4 filesystem, was finally released on 25 December 2008. On 15 January 2010, Google announced that it would upgrade its storage infrastructure from ext2 to ext4. On 14 December 2010, Google also announced it would use ext4, instead of YAFFS, on Android 2.3.
- Large file system
- The ext4 filesystem can support volumes with sizes up to 1 exbibyte (EiB) and single files with sizes up to 16 tebibytes (TiB) with the standard 4 KiB block size. The maximum file, directory, and filesystem size limits grow at least proportionately with the filesystem block size up to the maximum 64 KiB block size available on ARM and PowerPC/Power ISA CPUs.
- Extents replace the traditional block mapping scheme used by ext2 and ext3. An extent is a range of contiguous physical blocks, improving large file performance and reducing fragmentation. A single extent in ext4 can map up to 128 MiB of contiguous space with a 4 KiB block size. There can be four extents stored directly in the inode. When there are more than four extents to a file, the rest of the extents are indexed in a tree.
- Backward compatibility
- ext4 is backward-compatible with ext3 and ext2, making it possible to mount ext3 and ext2 as ext4. This will slightly improve performance, because certain new features of the ext4 implementation can also be used with ext3 and ext2, such as the new block allocation algorithm, without affecting the on-disk format.
- ext3 is partially forward-compatible with ext4. Practically, ext4 will not mount as an ext3 filesystem out of the box, unless certain new features are disabled when creating it, such as
- Persistent pre-allocation
- ext4 can pre-allocate on-disk space for a file. To do this on most file systems, zeroes would be written to the file when created. In ext4 (and some other files systems such as XFS)
fallocate(), a new system call in the Linux kernel, can be used. The allocated space would be guaranteed and likely contiguous. This situation has applications for media streaming and databases.
- Delayed allocation
- ext4 uses a performance technique called allocate-on-flush, also known as delayed allocation. That is, ext4 delays block allocation until data is flushed to disk. (In contrast, some file systems allocate blocks immediately, even when the data go into a write cache.) Delayed allocation improves performance and reduces fragmentation by effectively allocating larger amounts of data at a time.
- Unlimited number of subdirectories
- Ext4 does not limit the number of subdirectories in a single directory, except by the inherent size limit of the directory itself. (In ext3 a directory can have at most 32,000 subdirectories.) To allow for larger directories and continued performance, ext4 in Linux 2.6.23 and later turns on HTree indices (a specialized version of a B-tree) by default, which allows directories up to approximately 10-12 million entries to be stored in the 2-level HTree index and 2GB directory size limit for 4 KiB block size, depending on the filename length. In Linux 4.12 and later the
largedirfeature enabled a 3-level HTree and directory sizes over 2GB, allowing approximately 6 billion entries in a single directory.
- Journal checksumming
- ext4 uses checksums in the journal to improve reliability, since the journal is one of the most used files of the disk. This feature has a side benefit: it can safely avoid a disk I/O wait during journaling, improving performance slightly. Journal checksumming was inspired by a research paper from the University of Wisconsin, titled IRON File Systems (specifically, section 6, called "transaction checksums"), with modifications within the implementation of compound transactions performed by the IRON file system (originally proposed by Sam Naghshineh in the RedHat summit).
- Metadata checksumming
- Since Linux kernel 3.16.
- Faster file system checking
- In ext4 unallocated block groups and sections of the inode table are marked as such. This enables e2fsck to skip them entirely and greatly reduces the time it takes to check the file system. Linux 2.6.24 implements this feature.
- Multiblock allocator
- When ext3 appends to a file, it calls the block allocator, once for each block. Consequently, if there are multiple concurrent writers, files can easily become fragmented on disk. However, ext4 uses delayed allocation which allows it to buffer data and allocate groups of blocks. Consequently, the multiblock allocator can make better choices about allocating files contiguously on disk. The multiblock allocator can also be used when files are opened in O_DIRECT mode. This feature does not affect the disk format.
- Improved timestamps
- As computers become faster in general and as Linux becomes used more for mission-critical applications, the granularity of second-based timestamps becomes insufficient. To solve this, ext4 provides timestamps measured in nanoseconds. In addition, 2 bits of the expanded timestamp field are added to the most significant bits of the seconds field of the timestamps to defer the year 2038 problem for an additional 408 years.
- ext4 also adds support for time-of-creation timestamps. But, as Theodore Ts'o points out, while it is easy to add an extra creation-date field in the inode (thus technically enabling support for these timestamps in ext4), it is more difficult to modify or add the necessary system calls, like stat() (which would probably require a new version) and the various libraries that depend on them (like glibc). These changes will require coordination of many projects. Therefore, the creation date stored by ext4 is currently only available to user programs on Linux via the
- Transparent encryption
- Support for transparent encryption was added in Linux kernel 4.1 on June 2015.
In 2008, the principal developer of the ext3 and ext4 file systems, Theodore Ts'o, stated that although ext4 has improved features, it is not a major advance, it uses old technology, and is a stop-gap. Ts'o believes that Btrfs is the better direction because "it offers improvements in scalability, reliability, and ease of management." Btrfs also has "a number of the same design ideas that reiser3/4 had". However, ext4 has continued to gain new features such as file encryption and metadata checksums.
The ext4 file system does not honor the "secure deletion" file attribute, which is supposed to cause overwriting of files upon deletion. A patch to implement secure deletion was proposed in 2011, but did not solve the problem of sensitive data ending up in the file system journal.
Delayed allocation and potential data loss
Because delayed allocation changes the behavior that programmers have been relying on with ext3, the feature poses some additional risk of data loss in cases where the system crashes or loses power before all of the data has been written to disk. Due to this, ext4 in kernel versions 2.6.30 and later automatically handles these cases as ext3 does.
The typical scenario in which this might occur is a program replacing the contents of a file without forcing a write to the disk with fsync. There are two common ways of replacing the contents of a file on Unix systems:
fd=open("file", O_TRUNC); write(fd, data); close(fd);
- In this case, an existing file is truncated at the time of open (due to
O_TRUNCflag), then new data is written out. Since the write can take some time, there is an opportunity of losing contents even with ext3, but usually very small. However, because ext4 can delay writing file data for a long time, this opportunity is much greater.
- There are several problems that can arise:
- If the write does not succeed (which may be due to error conditions in the writing program, or due to external conditions such as a full disk), then both the original version and the new version of the file will be lost, and the file may be corrupted because only a part of it has been written.
- If other processes access the file while it is being written, they see a corrupted version.
- If other processes have the file open and do not expect its contents to change, those processes may crash. One notable example is a shared library file which is mapped into running programs.
- Because of these issues, often the following idiom is preferred over the one above:
fd=open("file.new"); write(fd, data); close(fd); rename("file.new", "file");
- A new temporary file ("file.new") is created, which initially contains the new contents. Then the new file is renamed over the old one. Replacing files by the
rename()call is guaranteed to be atomic by POSIX standards – i.e. either the old file remains, or it's overwritten with the new one. Because the ext3 default "ordered" journaling mode guarantees file data is written out on disk before metadata, this technique guarantees that either the old or the new file contents will persist on disk. ext4's delayed allocation breaks this expectation, because the file write can be delayed for a long time, and the rename is usually carried out before new file contents reach the disk.
fsync() more often to reduce the risk for ext4 could lead to performance penalties on ext3 filesystems mounted with the
data=ordered flag (the default on most Linux distributions). Given that both file systems will be in use for some time, this complicates matters for end-user application developers. In response, ext4 in Linux kernels 2.6.30 and newer detect the occurrence of these common cases and force the files to be allocated immediately. For a small cost in performance, this provides semantics similar to ext3 ordered mode and increases the chance that either version of the file will survive the crash. This new behavior is enabled by default, but can be disabled with the "noauto_da_alloc" mount option.
The new patches have become part of the mainline kernel 2.6.30, but various distributions chose to backport them to 2.6.28 or 2.6.29.
These patches don't completely prevent potential data loss or help at all with new files. The only way to be safe is to write and use software that does
fsync() when it needs to. Performance problems can be minimized by limiting crucial disk writes that need
fsync() to occur less frequently.
Linux kernel Virtual File System is a subsystem or layer inside of the Linux kernel. It is the result of the very serious attempt to integrate multiple file systems into an orderly single structure. The key idea, which dates back to the pioneering work done by Sun Microsystems employees in 1986, is to abstract out that part of the file system that is common to all file systems and put that code in a separate layer that calls the underlying concrete file systems to actually manage the data.
All system calls related to files (or pseudo files) are directed to the Linux kernel Virtual File System for initial processing. These calls, coming from user processes, are the standard POSIX calls, such as
Compatibility with Windows and Macintosh
ext4 does not yet have as much support as ext2 and ext3 on non-Linux operating systems. ext2 and ext3 have stable drivers such as Ext2IFS, which are not yet available for ext4. It is possible to create compatible ext4 filesystems by disabling the extents feature, and sometimes specifying an inode size. Another option for using ext4 in Windows is to use Ext2Fsd, an open-source driver that supports writing in ext4 partitions with limited journaling. Viewing and copying files from ext4 to Windows, even with extents enabled, is also possible with the Ext2Read software. More recently Paragon released its commercial product ExtFS for Windows which allows read/write capabilities for ext2/3/4.
macOS has full ext2/3/4 read–write capability through the Paragon ExtFS software, which is a commercial product. Free software such as ext4fuse has only read-only support with limited functionality.
- Comparison of file systems
- Extended file attributes
- List of file systems
- Previously, Linux used the same GUID for the data partitions as Windows (Basic data partition: EBD0A0A2-B9E5-4433-87C0-68B6B72699C7). Linux never had a separate unique partition type GUID defined for its data partitions. This created problems when dual-booting Linux and Windows in UEFI-GPT setup. The new GUID (Linux filesystem data: 0FC63DAF-8483-4772-8E79-3D69D8477DE4) was defined jointly by GPT fdisk and GNU Parted developers. It is identified as type code 0x8300 in GPT fdisk. (See definitions in gdisk's parttypes.cc)
- "DiscoverablePartitionsSpec". www.freedesktop.org. Retrieved 7 April 2018.
- "ext4: Fix handling of extended tv_sec". Linux-stable kernel tree. Retrieved 14 February 2017.
- Mathur, Avantika; Cao, MingMing; Bhattacharya, Suparna; Dilger, Andreas; Zhuravlev (Tomas), Alex; Vivier, Laurent (2007). "The new ext4 filesystem: current status and future plans" (PDF). Proceedings of the Linux Symposium. Ottawa, ON, CA: Red Hat. Archived from the original (PDF) on 6 July 2010. Retrieved 15 January 2008.
- Torvalds, Linus (9 June 2006). "extents and 48bit ext3". Linux kernel mailing list.
- Ts'o, Theodore (28 June 2006). "Proposal and plan for ext2/3 future development work". Linux kernel mailing list.
- Leemhuis, Thorsten (23 December 2008). "Higher and further: The innovations of Linux 2.6.28 (page 2)". Heise Online. Archived from the original on 3 January 2009. Retrieved 9 January 2010.
- "ext4: Rename ext4dev to ext4". Linus' kernel tree. Retrieved 20 October 2008.
- Leemhuis, Thorsten (23 December 2008). "Higher and further: The innovations of Linux 2.6.28". Heise Online.
- Paul, Ryan (15 January 2010). "Google upgrading to Ext4, hires former Linux Foundation CTO". Ars Technica.
- "Android 2.3 Gingerbread to use Ext4 file system". The H Open. 14 December 2010.
- "Migrating to Ext4". DeveloperWorks. IBM. Archived from the original on 1 December 2008. Retrieved 14 December 2008.
- Hal Pomeranz (28 March 2011). "Understanding EXT4 (Part 3): Extent Trees". SANS Digital Forensics and Incident Response Blog.
- "Mount of ext4 (created without extents) as ext3 fails on RH6.2". www.linuxquestions.org. Retrieved 7 April 2018.
- Prabhakaran, Vijayan; et al. "IRON File Systems" (PDF). CS Dept, University of Wisconsin.
- Ts'o, Theodore (5 October 2006). "Re: creation time stamps for ext4 ?".
- Edge, Jake (31 March 2017). "Extending statx()".
- Ts'o, Theodore (8 April 2015). "Ext4 encryption".
- Paul, Ryan (14 April 2009). "Panelists ponder the kernel at Linux Collaboration Summit". Ars Technica. Retrieved 22 August 2009. }}
- Theodore Ts'o (1 August 2008). "Re: reiser4 for 2.6.27-rc1". linux-kernel (Mailing list). Retrieved 31 December 2010.
- Corbet, Jonathan (11 October 2011). "Securely deleting files from ext4 filesystems".
- "ext4 documentation in Linux kernel source". 28 March 2009.
- Ubuntu bug #317781 Long discussion between Ubuntu developers and Theodore Ts'o on potential data loss
- Thoughts by Ted blog entry, 12 March 2009 A blog posting of Theodore Ts'o on the subject
- "How to read Ext3/Ext4 linux partition from windows 7 - Ubuntu Geek". www.ubuntugeek.com. Retrieved 7 April 2018.
- "Ext2Fsd Project". Ext2fsd.com. Retrieved 15 January 2012.
- Description of Ext4 compatibility with Windows 7, 1 November 2009 Archived 23 October 2011 at the Wayback Machine
- "Write/read access to Linux files under macOS High Sierra – extFS by Paragon Software for Mac". paragon-software.com. Retrieved 7 April 2018.
- Theodore Ts'o's discussion on ext4, 29 June 2006
- "ext4 online defragmentation" (materials from Ottawa Linux Symposium 2007)
- "The new ext4 filesystem: current status and future plans" (materials from Ottawa Linux Symposium 2007)
- Kernel Log: Ext4 completes development phase as interim step to btrfs, 17 October 2008
- "Ext4 block and inode allocator improvements" (materials from Ottawa Linux Symposium 2008)
- "Ext4: The Next Generation of Ext2/3 Filesystem"
- Ext4 (and Ext2/Ext3) Wiki
- Ext4 wiki at kernelnewbies.org
- Native Windows port of Ext4 and other FS in CROSSMETA
- Ext2read A windows application to read/copy ext2/ext3/ext4 files with extent and LVM2 support.
- Ext2Fsd Open source ext2/ext3/ext4 read/write file system driver for Windows. ext4 is supported from version 0.50 onwards
- Ext4fuse Open source read-only ext4 driver for FUSE. (Supports Mac OS X 10.5 and later, using MacFuse)