Having more than 128 files in the root directory corrupts the filesystem when reading or writing

1. Format a USB stick to FAT32.
2. Create 129 (or any higher number of) files in the root directory of the USB stick. Files can be anything, even empty ones. Filenames also can be anything, even file1, file2, …
3. Plug in the USB stick to an Android device.
4. Initialize the UsbMassStorageDevice as in documentation and print the storageDevice.partitions[0].fileSystem.rootDirectory.listFiles().size. Instead of printing the real number of files, it prints that number modulo 128 (e.g., if you have 129 files on the USB stick, it prints 1, and so on). If you try to read or write any files then, it corrupts the filesystem on the USB stick.

[stbelousov]

The bug is there: https://github.com/tracmap/libaums/blob/develop/libaums/src/main/java/com/github/mjdev/libaums/driver/scsi/ScsiBlockDevice.kt#L258

inBuffer may already contain data from previous reads (e.g., when we call rootDirectory.listFiles(), and filenames span over multiple clusters). inBuffer.clear() wipes all that data.

[devkumar2486]

[@magnusja I also faced the issue reported by @stbelousov, If we put more than 100 files in usb, we get count of lesser files and also the rest of the files got deleted, number of files are not fixed, so it may also depends on size of files or how the files are stored in usb, also I found that most of the time the name of last file remain in the usb get changed, I used 300 small size image from this zip small-size_300_images.zip After scan only 45 images remain in the usb from file “gen_257_1604472283911.jpg” to “gen_300_1604472289002.jpg” (44 files) and “gen_2~6.jpg” (original name of the file was “gen_256_1604472283828.jpg”) this supports this comment https://github.com/magnusja/libaums/issues/298#issuecomment-849216577 Finally I used the fix provided by @stbelousov in his fork https://github.com/tracmap/libaums/commit/7b9219106419142dec6b1a179067037a9e73c18d and this solved the issue for me. I suggest you to integrate his fix in the repo ASAP. Thanks in advance, also thanks to @stbelousov for providing fix