{"id":120974,"date":"2024-12-13T15:46:01","date_gmt":"2024-12-13T13:46:01","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-otkazoustojchivoj-fajlovoj-sistemy-littlefs-2-10"},"modified":"2024-12-13T15:46:01","modified_gmt":"2024-12-13T13:46:01","slug":"vypusk-otkazoustojchivoj-fajlovoj-sistemy-littlefs-2-10","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-otkazoustojchivoj-fajlovoj-sistemy-littlefs-2-10","title":{"rendered":"Release of the fault-tolerant file system LittleFS 2.10","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of the LittleFS 2.10 project has been published, developing a compact file system for embedded devices and microcontrollers. Initially, the file system was created by ARM for the Mbed OS operating system, but was later separated into its own project. The FS code is written in C and is distributed under the BSD license. The reference implementation of LittleFS is provided as a C library, on the basis of which a FUSE module and bindings for various programming languages have been created. <\/p>\n
Features of LittleFS: <\/p>\n
\n
Low resource requirements and support for operation with limited RAM size. The LittleFS implementation uses only statically defined buffers (without dynamic memory allocation) and does not use recursive calls, which means that the amount of RAM consumed and the service structures of LittleFS on the storage device remain constant, regardless of what is recorded in the FS and the size of the storage.\n
Wear leveling mechanisms for Flash media that minimize the reuse of blocks and evenly distribute block erasure operations in Flash memory, where the controller does not provide a solution for this task.\n
Very high fault tolerance \u2014 the filesystem considers unexpected shutdowns (termination through power loss) as normal situations and ensures that the disk storage remains intact at all times. To prevent data integrity violations and loss, a copy-on-write (COW) mechanism is used, where changes do not overwrite existing information but are saved in a new location.\n
Atomicity of operations such as deletion and renaming, even in the case of power loss during their execution. Changes to a file are flushed to disk only after the sync or close call. Inconsistencies caused by operations that cannot be performed atomically are handled by a special deorphan handler, which traverses the entire FS tree after boot.\n
Support for POSIX-like functions for working with files and directories. <\/ul>\n
The contents of the files in LittleFS are represented by COW lists CTZ, providing a complexity level of O(1) for adding and O(nlogn) for reading. Block allocation is done by scanning the filesystem for used blocks within a fixed-size area, stored as a bit vector. To simplify scanning, all directories are part of a linked list that encompasses the entire filesystem. If an error occurs while writing a block, a new block is allocated and the data is transferred to it. <\/p>\n
Among the changes in the new version of LittleFS: <\/p>\n
\n
The code for parsing file paths has been redesigned, bringing the behavior of the filesystem closer to POSIX systems and user expectations in situations such as path termination with a slash, handling empty paths, and navigating beyond the root of the filesystem.\n
Two new examples of block devices, ramcrc32bd and ramrsbd, have been added, implementing an error correction mechanism compatible with LittleFS. Currently, the LittleFS filesystem does not support error detection and correction, and these operations are handled at the block device level.\n
The lfs_mkdir function has been updated to support trailing slashes, i.e., calling lfs_mkdir(«a\/») no longer results in an error.\n
In the lfs_stat and lfs_getattr functions, an error will now be output when trailing slashes are used if the existing path in the filesystem is not a directory.\n
Attempting to open a file with a trailing slash in its name via the lfs_file_open function will now result in an error LFS_ERR_NOTDIR if the file is not a directory in the filesystem, LFS_ERR_ISDIR if the name refers to a directory in the filesystem, and LFS_O_CREAT if the file does not exist.\n
Attempting to access outside the root filesystem, for example, lfs_stat(«\/..\/a»), will now result in an error.\n
Specifying an empty path is no longer synonymous with accessing the root directory, meaning that calling lfs_stat(«») will result in an error. <\/ul>\n