search

vrunkel / F3XSwift

macOS GUI to the f3 - Fight Flash Fraud - tool and based on F3X
GNU General Public License v3.0
152 stars 8 forks source link

Left test file on USB drive after successful test completion #8

Open drjasonharrison opened 1 year ago

drjasonharrison commented 1 year ago

I'm not sure if this is a F3 issue or F3xSwift issue.

After the completion of a successful test, a large test file remained, completely filling the USB drive.

I expect that any test files would be removed.

robertlipe commented 1 year ago

I think that's intended behaviour. It allows you to check the box to "skip write test" and just proceed directly to the read test if you need to repeat the test for read-only. It's also handy for investigation to be able to see the file that was written by earlier passes.

https://github.com/vrunkel/F3XSwift/blob/main/docs/usage.md

says, "ead test uses f3read and can be started without writing if your sd card already has the test files."

While I don't have any authoritative say (hey, I'm just a user, too, and not a developer or owner or anybody important...) I consider the current behaviour to be intentional, correct, and documented, though it may, admittedly, violate the principle of least surprise to not at least offer to clean up after itself.

It's additionally complicated on MacOS because if you delete the files in the "obvious" way on MacOS (via Finder) the files don't ACTUALLY get deleted, they get renamed into some .Trashes/SOMETHING directory so that you can undelete them if you need to. Great feature in MacOS if you're trying to rescue a single file on a 10TB drive. Terrible feature if you're trying to empty a small stick because you'll find the stick is still full-ish because it still contains the file[s], just in an annoying location.