{"push_id":2563189132,"size":1,"distinct_size":1,"ref":"refs/heads/fat-erase-disk","head":"e77d57e0bceb81369836e7f50b19897ce6d27ee5","before":"b567ce46fd8d5416dee028583ef433b9deef1690","commits":[{"sha":"e77d57e0bceb81369836e7f50b19897ce6d27ee5","author":{"name":"Christopher Haster","email":"3c6042e697f5985911c307b6ac6f18203c312263@utexas.edu"},"message":"fatfs: Added erase disk to format\n\nRight now, many users are trying out many different filesystems.\nUnfortunately, this can leave partially written filesystems on disk\nin various states.\n\nA very common pattern for using embedded filesystems is to attempt\na mount, and on failure, format the storage with the filesystem.\n\nUnfortunately, this simply doesn't work if you try to change the\nfilesystem being used on a piece of storage. Filesystems don't always\nuse the same regions of storage, and can leave enough metadata lying\naround from old filesystems to trick a different mount into thinking a\nvalid filesystem exists on disk. The filesystems we have were never\ndesigned to check for malicious modification and can't protect against\narbitrary changes.\n\nThat being said, it's caused enough problems for users, so as a\nworkaround this patch adds a disk erase to the FAT filesystem format.\nThe most common error happens when you use LittleFS, followed by FAT,\nfollowed again by LittleFS.\n\nNo other combination of filesystem usage has shown a similar failure,\nbut it is possible after extensive filesystem use, so it is still\nsuggested to force a format of the storage when changing filesystems.","distinct":true,"url":"https://api.github.com/repos/geky/mbed/commits/e77d57e0bceb81369836e7f50b19897ce6d27ee5"}]}
{"actor":{"display_login":"geky"}}