4 ms·
The problem with this filesystem is that it doesn't actually protect against power fails. Mostly you are OK, but not always. I run an afl-base fuzzer against i
by pjsg 5y ago
The problem with this filesystem is that it doesn't actually protect against power fails. Mostly you are OK, but not always.
I run an afl-base fuzzer against it back in 2020, and found a bunch of issues leading to assert failures in the code. I wasn't even checking data integrity. The tickets are still open (and it wasn't obvious to me how to fix them).
Spiffs is another micro controller file system, but it also fails fuzzing tests very rapidly with various failures. Spiffs seems less maintained than littlefs.
Are there any other good, reliable, freely licensed, microcontroller file systems suitable for small flash parts?
- deleted 5y ago[deleted]
- deleted 5y ago[deleted]
- pvarangot 5y agoI used it at work twice and it was mostly ok with power failures, thing is you have to be careful if you are mounting it very early on boot if your embedded OS can bootloop fast after LFS is already mounted, because if you nuke it with a flurry of power fails it will break. For example if you have a battery you probably want to be sure you have a reliable measurement for SoC and enough juice to stay up before you mount LFS.
- bsder 5y ago> The problem with this filesystem is that it doesn't actually protect against power fails. Mostly you are OK, but not always. Power failure is a tough problem in embedded file systems (aka--too small for Linux). Effectively--you need to be "append-only with checksums at checkpoints". Every one of those words is anathema to making your flash small and cheap.