On Sat, Feb 12, 2011 at 11:45:41AM +0100, Arnd Bergmann wrote: > * The FAT location is clearly visible in a number of tests > done inside of an allocation unit. It's normally slower for > linear access, but faster for random access. Sometimes > reading the FAT is also slower than reading elsewhere. I wouldn't also be surprised if there's some cards out there which parse the FAT being written, and start activities (such as erasing clusters) based upon changes therein. Such cards would be unsuitable for use with non-FAT filesystems. It might be worth devising some sort of check for this kind of behaviour. Unrelated, I have a USB based device which provides an emulated FAT filesystem - all files except one on this filesystem are read-only. The writable file is a textual configuration file. It can be reliably updated by Windows based systems, but updates from Linux based systems are ignored - presumably because updates to the FAT/directory/data clusters are occuring in a different order. -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
