kyrreaa

I've removed the open/close/open as I found out it was created by someone before me in the project due to a bug they had elsewhere... (Did you know that some...

Well, if you already have some file content planned I see the idea but the api for FS in Zephyr for example does not allow for that. It does however...

> Yeah, POSIX expects open to create a file, so I think you're right. But given the number of issues that have been opened over this, I think avoiding 0-sized...

Just to note that this "issue" still persist in 2.8.1 tested as of today. It is absolutely caused by the garbage collection / compacting of the logs but I don't...

What about the variable skip block section of each block. This varies with block number and basically grows with size of file?

Yeah I figured the number of pointers based on the block number outwards counting trailing zeroes in block number and add one. Since it is a bit convoluted the cost...

Do you monitor the result of writes and close? Could the system be running out of space? Edit: Every time you overwrite the file you essentially create new blocks and...

If you write a NAND access layer for it to init the flash and provide the read, write and erase functions then LittleFS should not care what the underlying storage...

Thank you @geky that is very useful to know. It also explains why I had some issues with my access layer before as I had done a naive implementation assuming...

I would love for an option to turn off the cloning and instead make a temporary copy of the affected block(s) and upon commit/sync copy those blocks back over the...