You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that the solution is to runs SPIFFS_check after restarting. My concern is that this could be slow. In particular, this might cause problems in systems which go into deep sleep and are then woken up (when, presumably, the filesystem is actually in a good state). The issue is that we need to read from the filesystem to get the init.lua.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Nope. SPIFFS is not a journaling FS, so there is no transactional integrity around writes to the FS. The read, write and erase primitives simply call the SDK API calls for these operations. Power failure during write or erase can leave the FS in an unknown and potentially corrupt state, though the logical design attempts to mitigate these issues. See How does SPIFFS handle powerlosses?.
See pellepl/spiffs#137
It appears that the solution is to runs SPIFFS_check after restarting. My concern is that this could be slow. In particular, this might cause problems in systems which go into deep sleep and are then woken up (when, presumably, the filesystem is actually in a good state). The issue is that we need to read from the filesystem to get the init.lua.
The text was updated successfully, but these errors were encountered: