Comment 2 for bug 588348

> The current process is to format the disk which unmounts it, formats it as FAT32, and mounts it.
Thereafter, usb-creator generates md5sums and copies the files to the usb disk. Immediately after writing, it attempts to verify the integrity of those written files by checking the md5sums.

Unfortunately those files may still be in the cache, which makes checking the md5sums pointless.

The method I used to manually verify the files was to eject the disk, remove and re-insert the disk then run
md5sum -c md5sum.txt

I propose that after writing the files to disk, usb-creator should flush the cache before checking the md5sums.
I believe the way of doing this is to unmount and then re-mount the disk, or possibly the following programmatically:
http://linux-mm.org/Drop_Caches

Incidentally, I do not believe palimpsest is able to detect these "soft" bad blocks.