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
"During our regression testing, repeatedly powering off the ECU abruptly while LFS operations were in progress caused the filesystem to become unwritable."
#1088
We are encountering a peculiar issue with our LFS integration on Serial EEPROM. During our regression testing, repeatedly powering off the ECU abruptly while LFS operations such as writing or deleting files are in progress causes the filesystem to become unwritable after several cycles. Although we can still read most of the other files, attempting to write a new file results in an exception, as shown in the attached image. Any assistance in understanding the cause or any pointers would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
So apparently what appears is, if a block that contains metadata is somehow overwritten then there are no checks on when the pointers get used and hence it results in this erroneous behavior, but for now once we corrected the logic to ensure block write is proper, we are able to overcome this issue. so closing the issue for now, but it can be a future improvement in how the pointers are checked before use in littlefs, specifically the next pointers.
Hi,
We are encountering a peculiar issue with our LFS integration on Serial EEPROM. During our regression testing, repeatedly powering off the ECU abruptly while LFS operations such as writing or deleting files are in progress causes the filesystem to become unwritable after several cycles. Although we can still read most of the other files, attempting to write a new file results in an exception, as shown in the attached image. Any assistance in understanding the cause or any pointers would be greatly appreciated.
The text was updated successfully, but these errors were encountered: