NILFS

"NILFS is a log-structured filesystem, in that the storage medium is treated like a circular buffer and new blocks are always written to the end.[…]Log-structured filesystems are often used for flash media since they will naturally perform wear-leveling;[…]NILFS emphasizes snapshots. The log-structured approach is a specific form of copy-on-write behavior, so it naturally lends itself to the creation of filesystem snapshots. The NILFS developers talk about the creation of "continuous snapshots" which can be used to recover from user-initiated filesystem problems[…]."[1]

Using a copy-on-write technique known as "nothing in life is free", NILFS records all data in a continuous log-like format that is only appended to, never overwritten, an approach that is designed to reduce seek times, as well as minimize the kind of data loss that occurs after a crash with conventional file systems. For example, data loss occurs on ext3 file systems when the system crashes during a write operation. When the system reboots, the journal notes that the write did not complete, and any partial data writes are lost.

Some file systems, like UFS-derived file systems used by the Solaris operating system and BSDs, provide a snapshot feature that prevents such data loss, but the snapshot configuration can be lengthy on large file systems. NILFS, in contrast, can "continuously and automatically [save] instantaneous states of the file system without interrupting service", according to NTT Labs.[2]

The "instantaneous states" that NILFS continuously saves can actually be mounted, read-only, at the same time that the actual file system is mounted read-write — a capability useful for data recovery after hardware failures and other system crashes. The "lscp" (list checkpoint) command of an interactive NILFS "inspect" utility is first used to find the checkpoint's address, in this case "2048":

# inspect /dev/sda2
...
nilfs> listcp
   1     6 Tue Jul 12 14:55:57 2005 MajorCP|LogiBegin|LogiEnd
2048  2352 Tue Jul 12 14:55:58 2005 MajorCP|LogiEnd
...
nilfs> quit

The checkpoint address is then used to mount the checkpoint:

# mount -t nilfs -r -o cp=2048 /dev/sda2 /nilfs-cp
# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda2             70332412   8044540  62283776  12% /nilfs
/dev/sda2             70332412   8044540  62283776  12% /nilfs-cp

NILFS provides continuous snapshotting. In addition to versioning capability of the entire file system, users can even restore files mistakenly overwritten or deleted at any recent time. Since NILFS can keep consistency like conventional LFS, it achieves quick recovery after system crashes.

Continuous snapshotting is a not provided by most filesystem, including those supporting point-in-time snapshotting (e.g. Btrfs)

NILFS creates a number of checkpoints every few seconds or per synchronous write basis (unless there is no change). Users can select significant versions among continuously created checkpoints, and can change them into snapshots which will be preserved until they are changed back to checkpoints.

There is no limit on the number of snapshots until the volume gets full. Each snapshot is mountable as a read-only file system. It is mountable concurrently with a writable mount and other snapshots, and this feature is convenient to make consistent backups during use.

Possible uses of NILFS include versioning, tamper detection, SOX compliance logging, data loss recovery.

The current major version of NILFS is version 2, which is referred to as NILFS2. NILFS2 implements online garbage collection to reclaim disk space with keeping multiple snapshots.

Other NILFS features include:

• B-tree based file and inode management.
• Immediate recovery after system crash.
• 64-bit data structures; support many files, large files and disks.
• 64-bit on-disk timestamps which are free of the year 2038 problem.

• NILFS was merged into the Linux kernel 2.6.30.[5]
• On distributions where NILFS is available out-of-the-box, the user needs to download the nilfs-utils (or nilfs-tools) package, following the instructions from .

A separate, BSD licensed implementation, currently with read-only support, is included in NetBSD.[6]

In the January 2015 presentation SD cards and filesystems for embedded systems at Linux.conf.au, it was stated:[7]

If you've got a workload that's latency sensitive, you might want to use NILFS. If you've got one that's throughput sensitive, you might want to use F2FS.

— Peter Chubb

NILFS2 works much better for the lots of small files case than F2FS or EXT4.

— Peter Chubb

The NILFS2 filesystem utilities are made available under the GNU Public License version 2, with the exception of the lib/nilfs libraries and their header files, which are made available under the GNU Lesser General Public License Version 2.1.

The Japanese primary authors and major contributors to the nilfs-utils who worked or are working at labs of NTT Corporation are:

• Ryusuke Konishi (Primary maintainer, 02/2008-Present)
• Koji Sato
• Naruhiko Kamimura
• Seiji Kihara
• Yoshiji Amagai
• Hisashi Hifumi and
• Satoshi Moriai.

Other major contributors are:

• Andreas Rohner [8]
• Dan McGee
• David Arendt
• David Smid
• dexen deVries
• Dmitry Smirnov
• Eric Sandeen
• Jiro SEKIBA
• Matteo Frigo
• Hitoshi Mitake
• Takashi Iwai
• Vyacheslav Dubeyko

• ZFS
• Btrfs
• List of file systems
• Comparison of file systems
• Log-structured File System (BSD)
• Sprite operating system

• Official website
• "An Article Describing High-level Features". Archived from the original on 2013-01-03.
• "World's Largest TELCO Joins Open Source Development Labs". Archived from the original on 2013-01-27.
• NILFS: A File System to Make SSDs Scream
• Manjaro tutorial NILFS: A filesystem designed to minimize the likelyhood [sic] of data loss