> if the implementation follows the recommended write ordering of allocation bitmap → FAT → directory entry when creating a file and the reverse when deleting a

> if the implementation follows the recommended write ordering of allocation bitmap → FAT → directory entry when creating a file and the reverse when deleting a file, then even interrupted writes do not pose an issue. The problem is that with all the caching that occurs, writes do not happen in this straightforward way unless the cache is completely flushed at each point. Even getting cached flushed is not straightforward because most drives cache and some ignore cache flushes to increase performance.