geeksville

hmm this is less that perfect (though quite possibly unrelated to the problem): ``` // brief window of risk here ;-) if (FSCom.exists(filename) && !FSCom.remove(filename)) { LOG_WARN("Can't remove old pref...

@ImprobableStudios thank you for your report. I'm eager to help look into this but alas I'm doing powermon/structured logging/power measurements for another weekish. @thebentern and I have been talking about...

and some copypasta from our chat so I don't forget it: a slight reformatting of the list of options I could think of (ya'll can think of others possibly!): it...

Hmm - the adafruit fork of littlefs is quite old (last commit to their lfs.c was **five years ago** and the main littlefs project has many fixes which are not...

Some other misc comments for when someone gets to looking at this: * Check the adafruit threads above wrt the relationship between Bluefruit (and SoftDevice?) LFS usage and the adafruit...

btw: the 'good' news is that I can pretty easily reproduce this bug by power cycling a rak4630 (noticed while doing my power testing). I'm still planning on working on...

oh: interesting: I can cause this corruption by performing a filesystem write 100% of the time on rak4630 by doing a write while the battery voltage is down at 3.2V.

imo this is definitely it. over the next couple of days I'll add some instrumentation (both with the oscope and in sw to print vcc voltage via a ADC). Then...

Important Note: BatmansWang on discord reports having corruption without low batteries so there might be something else going on (possibly not related to voltage, possibly still related - tbd)

# Loss of config due to filesystem size limits (Any comments/advice on the notes below are apprecated!) (This is distinct from the 'loss of config due to low-power filesystem corruption'...