Deomid Ryabkov
Deomid Ryabkov
so do you then recommend that SPIFFS_check be run on every mount?
the practical upshot of it that files just go missing and device gets bricked... not ideal :)
yeah, same here. there's no way to tell, in general. so - any chance that GC can be modified to not require a check? also, how expensive is check? doing...
as providers of middleware, we unfortunately cannot assume existence of energy-independent storage. i think i'll have to go with `SPIFFS_check` by default, for now.
this didn't go down very well. looks like `SPIFFS_check` has some sort of bug, because with the change above we started getting pretty frequent corruptions - even on planned and...
ok, let me close the loop on this last one: this was a false alarm, something else was wrong with the setup. i no longer suspect `SPIFFS_check`.
perhaps the latter (delete if `src != dst` and `dst` already exists) is simpler to implement.
> If requested ok, let me put in a request then :) we would like to stay on latest SPIFFS, but we have older builds of user firmware to consider...
yes, on target. OTA will come with new spiffs code and new fs image. new code boots and mounts the new fs, then it needs to mount the old FS...
yes, we reserve 2x the space for code and fs, to make sure we can revert in case of failed OTA.