New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All the data is lost after update from disk 2.0 to disk 2.1 #964
Comments
Does "Expanding superblock" occur in your log at all during this? If so #953 may be related (currently unsolved). What is most likely happening is something is corrupting one of the superblocks, causing littlefs to find/mount the older superblock. It's unlikely this is actually related to the commit that changes the version, most likely other state is rolling back as well. It would be very useful if you're able to reproduce this with a small example somehow. Also what is your config? block_size, block_count, block_cycles, etc? This is useful for looking for patterns with other bug reports. |
No, there was no "Expanding superblock" message in the debug log. The only messages I have reported above. 3 right after the update, and the same 3 after one of a lot of reboots.
The activity: The config:
All the new fields in 2.9.1 were set to 0. |
Attributes are not used. |
Right after the LittleFS update from version 2.4 to 2.9.1 it has written in debug:
And everything was ok, then after a lot of reboots, once the reboot happened during a write operation, it has written again:
and the FS is totally clean after that.
The text was updated successfully, but these errors were encountered: