Open Access Articles- Top Results for UBIFS


Developer Nokia with help of University of Szeged
Full name Unsorted Block Image File System
Introduced 2008 (Linux kernel 2.6.27)
Directory contents B+ trees
Allowed characters in filenames Any byte except NUL and forward slash "/"[citation needed]
Forks Yes
Attributes Yes
File system permissions POSIX
Supported operating systems Linux

The Unsorted Block Image File System (UBIFS) is a successor to JFFS2, and competitor to LogFS,[1] as a file system for use with raw flash memory media.[2] Development began in earnest in 2007, with the first stable release made to Linux kernel 2.6.27 in October 2008.[3] The file system is developed by Nokia engineers with help of the University of Szeged, Hungary.

Note that UBIFS works on top of an unsorted block images (UBI) device, which is itself on top of a memory technology device (MTD). MTDs are not to be used directly.[4] Two major differences between UBIFS and JFFS2 are that UBIFS supports write caching,[5] and UBIFS errs on the pessimistic side of free space calculation.[6] UBIFS tends to perform better than JFFS2 for large NAND FLASH devices.[7] This is a consequence of the UBIFS design goals:[8] faster mounting, quicker access to large files, and improved write speeds. UBIFS also preserves or improves upon JFFS2's on-the-fly compression, recoverability and power fail tolerance.[8] UBIFS's on-the-fly data compression allows zlib (deflate algorithm) or LZO.

JFFS2 stores filesystem indexes in memory whereas UBIFS stores indexes in flash.[9] This directly impacts the scalability of JFFS2 as the tables must be rebuilt every time the volume is mounted. Also, the JFFS2 tables may consume enough system RAM that some images may be unusable.

Unsorted Block Images

Unsorted block images (UBI)[10] is an erase block management layer for flash memory devices. UBI serves two purposes, tracking NAND flash bad blocks and providing wear leveling. Wear leveling spreads the erases and writes across the entire flash device. UBI presents logical erase blocks to higher layers and maps these to physical flash erase blocks. UBI was written specifically for UBIFS so that it does not have to deal with wear leveling and bad blocks. However, UBI may also be useful with cramfs and NAND flash; cramfs is not aware of NAND flash bad blocks.


UBI was augmented in Linux 3.7 with fastmap support. [11] [12] Fastmap maintains an on-disk version of information previously created in memory by scanning the entire flash device. The code falls back to the previous mechanism of a full scan on failures and older UBI systems will simply ignore the fastmap information.

See also

External links