mirror of https://github.com/ARMmbed/mbed-os.git
e77d57e0bc
Right now, many users are trying out many different filesystems. Unfortunately, this can leave partially written filesystems on disk in various states. A very common pattern for using embedded filesystems is to attempt a mount, and on failure, format the storage with the filesystem. Unfortunately, this simply doesn't work if you try to change the filesystem being used on a piece of storage. Filesystems don't always use the same regions of storage, and can leave enough metadata lying around from old filesystems to trick a different mount into thinking a valid filesystem exists on disk. The filesystems we have were never designed to check for malicious modification and can't protect against arbitrary changes. That being said, it's caused enough problems for users, so as a workaround this patch adds a disk erase to the FAT filesystem format. The most common error happens when you use LittleFS, followed by FAT, followed again by LittleFS. No other combination of filesystem usage has shown a similar failure, but it is possible after extensive filesystem use, so it is still suggested to force a format of the storage when changing filesystems. |
||
|---|---|---|
| .. | ||
| FEATURE_BLE | ||
| FEATURE_COMMON_PAL | ||
| FEATURE_LWIP/lwip-interface | ||
| FEATURE_UVISOR | ||
| TESTS/filesystem | ||
| cellular | ||
| filesystem | ||
| frameworks | ||
| lorawan | ||
| mbedtls | ||
| nanostack | ||
| netsocket | ||
| nvstore | ||
| storage/FEATURE_STORAGE | ||
| unsupported | ||