tuxmain/website
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Update: links, reads, flash enc

Browse source
This commit is contained in:
Pascal Engélibert 2026-02-27 19:15:17 +01:00
commit 9916659c35
4 changed files with 28 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

4
content/blog/flash-filesystem-encryption/index.md
View file

@ -88,6 +88,10 @@ The problem is that flash memories are slow and become damaged after a limited n
#### A dedicated filesystem
> La peste soit du FAT !
>
>_Dom Juan_, Molière
Now that we've highlighted an important property of flash memories, it appears FAT32 may not be the best choice as a filesystem. Indeed, a modified block would stay at the same physical address, causing different regions of the storage to wear more rapidly than others. It would be better to spread the write operations across the entire space, in order to maximize the time before a failure happens.
[LittleFS](https://github.com/littlefs-project/littlefs) is made exactly for this purpose. Moreover, it provides atomic operations, meaning it never leaves the filesystem in an incoherent state if there is a power loss or a storage failure during a write operation.