This release brings in some useful community-driven features.
What's new?
Thanks to @BrianPugh, littlefs no longer needs the block_count when mounting an existing filesystem (#866)
Simply set block_count=0 in your configuration, and littlefs will automatically determine the block_count based on what's on disk. This allows you to mount a filesystem of unknown size.
Added lfs_fs_grow which allows you to change the size of an existing filesystem, thanks to @kaetemi (#872)
The main use case is for changing the size of a partition as storage requirements change.
Note: littlefs does not support shrinking a filesystem, and this is unlikely to change (it's a hard problem).
Added lfs_fs_gc which allows you to manually run the block allocator, thanks to @opilat (#875)
Note: littlefs currently does not persist any found free blocks to disk, though this may change in the future.
This limits the current value of lfs_fs_gc, but it may still be useful for moving the expensive block scan out of performance sensitive code paths.
This release brings in some useful community-driven features. Thanks everyone who has put up PRs!
Bringing in:
Draft of release notes follows:
This release brings in some useful community-driven features.
What's new?
Thanks to @BrianPugh, littlefs no longer needs the
block_count
when mounting an existing filesystem (#866)Simply set
block_count=0
in your configuration, and littlefs will automatically determine theblock_count
based on what's on disk. This allows you to mount a filesystem of unknown size.Added
lfs_fs_grow
which allows you to change the size of an existing filesystem, thanks to @kaetemi (#872)The main use case is for changing the size of a partition as storage requirements change.
Note: littlefs does not support shrinking a filesystem, and this is unlikely to change (it's a hard problem).
Added
lfs_fs_gc
which allows you to manually run the block allocator, thanks to @opilat (#875)Note: littlefs currently does not persist any found free blocks to disk, though this may change in the future.
This limits the current value of
lfs_fs_gc
, but it may still be useful for moving the expensive block scan out of performance sensitive code paths.