An editor has nominated this article for deletion.You are welcome to participate in the deletion discussion, which will decide whether or not to retain it.Feel free to improve the article, but do not remove this notice before the discussion is closed. For more information, see the guide to deletion.Find sources: "LogFS" – news · newspapers · books · scholar · JSTOR%5B%5BWikipedia%3AArticles+for+deletion%2FLogFS%5D%5DAFD
This article relies excessively on references to primary sources. Please improve this article by adding secondary or tertiary sources. Find sources: "LogFS" – news · newspapers · books · scholar · JSTOR (February 2013) (Learn how and when to remove this message)
Developer(s)Jörn Engel, Prasad Joshi
operating systems
Linux at the Wayback Machine (archived 2010-06-16)

LogFS is a Linux log-structured and scalable flash file system, intended for use on large devices of flash memory. It is written by Jörn Engel[1] and in part sponsored by the CE Linux Forum.

LogFS was introduced in the mainline Linux kernel in version 2.6.34, released on May 16, 2010. It was removed from the codebase during the merge window of version 4.10, in December 2016, because it was "unmaintained for years and seemingly unused".[2]


As of November 2008, LogFS was mature enough to pass its entire test suite, and was subsequently included in the mainline Linux kernel, marked as 'experimental', in version 2.6.34 released on May 16, 2010. However, it did not attract a large user base and was removed from the kernel in December 2016.


LogFS was motivated by the difficulties of JFFS2 with larger flash-memory drives. LogFS stores the inode tree on the drive; JFFS2 does not, which requires it to scan the entire drive at mount and cache the entire tree in RAM. For larger drives, the scan can take dozens of seconds and the tree can take a significant amount of main memory. LogFS avoids these penalties, but it does do more work while the system is running and uses some of the drive's space for holding the inode tree.

LogFS stores a file's inode tree on the drive, which means on a write to the file, each ancestor node in the tree must be rewritten. This is done by a "wandering tree" update. The lowest node in the tree (i.e., the data) is written first, each node is written ascending the tree, until the root inode is updated. Writing the root last maintains atomicity of the update.

A flash-memory block is the unit for erasures and is usually larger than the file-system block. LogFS handles this disparity by packing multiple file-system blocks into a single flash-memory block. A "sum" entry at the end of the flash-memory block records what data is stored in it. When the flash-memory block has all its file-system blocks moved or deleted, it can be erased and used for new data.

For peak usage of the flash-memory drive, it is necessary to compact data so that flash-memory blocks are full of useful data. This is accomplished by garbage collection. LogFS's garbage collection strategy relies on file data being placed in a certain way into flash-memory blocks: a flash-memory block will hold only file data from the same level in the inode tree. LogFS can garbage collect the top level of the trees using just 1 empty flash-memory block. It can garbage collect the top 2 levels of the trees using 2 empty flash-memory blocks. And can garbage collect all N levels of the trees using N empty flash memory blocks. The algorithm is exponential time in the worst case, but the worst case is rare and the algorithm requires reserving only a handful of flash-memory blocks.

See also


  1. ^ Jörn Engel; Robert Mertens (2005-09-18). "LogFS - finally a scalable flash filesystem" (PDF). ((cite journal)): Cite journal requires |journal= (help)
  2. ^ Jonathan Corbet (2016-12-21). "4.10 Merge window part 2". Retrieved 2020-06-02. The logfs filesystem, unmaintained for years and seemingly unused, has been removed from the kernel.