|Introduced||May 2010 with Linux 2.6|
|Partition identifier||0x83 (MBR)
|Directory contents||Table, hashed B-tree with dir_index enabled|
|File allocation||bitmap (free space), table (metadata), snapshots are allocated as files from the volume free space|
|Max. volume size||2 TB – 16 TB|
|Max. file size||2 TB|
|Max. number of files||Variable, allocated at creation time|
|Max. filename length||254 bytes|
|Allowed characters in filenames||All bytes except NULL and '/'|
|Dates recorded||modification (mtime), attribute modification (ctime), access (atime)|
|Date range||December 14, 1901 – January 18, 2038|
|Attributes||No-atime, append-only, synchronous-write, no-dump, h-tree (directory), immutable, journal, secure-delete, top (directory), allow-undelete|
|File system permissions||Unix permissions, ACLs and arbitrary security attributes (Linux 2.6 and later)|
|Transparent encryption||No (provided at the block device level)|
|Supported operating systems||Linux|
Next3 is a journaled file system for Linux based on ext3 which adds snapshots support, yet retains compatibility to the ext3 on-disk format. Next3 is implemented as open-source software, licensed under the GPL license.
A snapshot is a read-only copy of the file system frozen at a point in time. Versioning file systems like Next3 can internally track old versions of files and make snapshots available through a special namespace.
An advantage of copy-on-write is that when Next3 writes new data, the blocks containing the old data can be retained, allowing a snapshot version of the file system to be maintained. Next3 snapshots are created quickly, since all the data composing the snapshot is already stored; they are also space efficient, since any unchanged data is shared among the file system and its snapshots.
Dynamically Provisioned Snapshots Space
The traditional Linux Logical Volume Manager volume level snapshots implementation requires that storage space be allocated in advance. Next3 uses Dynamically provisioned snapshots, meaning it does not require pre-allocation of storage space for snapshots, instead allocating space as it is needed. Storage space is conserved by sharing unchanged data among the file system and its snapshots.
Since Next3 aims to be both forward and backward compatible with the earlier ext3, all of the on-disk structures are identical to those of ext3. The file system can be mounted for read by existing ext3 implementations with no modification. Because of that, Next3, like ext3, lacks a number of features of more recent designs, such as extents.
When there are no snapshots, Next3 performance is equivalent to ext3 performance. With snapshots, there is a minor overhead per write of metadata block (copy-on-write) and a smaller overhead (~1%) per write of data block (move-on-write).
As of 2011, Next4, a project for porting of Next3 snapshot capabilities to the Ext4 file system, is mostly completed. The porting is attributed to members of the Pune Institute of Computer Technology (PICT) and the Chinese Academy of Sciences.
- The maximum number of inodes (and hence the maximum number of files and directories) is set when the file system is created. If V is the volume size in bytes, then the default number of inodes is given by V/213 (or the number of blocks, whichever is less), and the minimum by V/223. The default was deemed sufficient for most applications. The max number of subdirectories in one directory is fixed to 32000.
- Corbet, Jonathan. "The Next3 filesystem". LWN.
- Next3: Ext3 with snapshots. The H Open. June 11, 2010
- Shread, Paul (June 8, 2010). "CTERA Adds Data Protection to Linux File Systems". Retrieved 9 June 2010.
- "Next3 FAQ".
- NEXT3 Filesystem Home Page