TrueCrypt provides an option to use a hidden operating system. This works by having a decoy operating system residing on partition 1, and using partition 2 as (encrypted) data storage for the decoy OS. The catch is, TrueCrypt makes it possible for the partition 2, the "outer" partition, also contain a hidden partition lurking within the outer partition's free space - which then contains the hidden operating system.
When mounting the outer partition as data storage, TrueCrypt is able to protect the hidden data if you provide the hidden partition's password. If this is not done, anything written to the free space of the outer partition may of course overwrite something from the hidden data. TrueCrypt, for security reasons, does not do the prevention by moving the free data around, or just avoiding the area where it's hidden - but only by detecting a conflict and preventing the write. In fact, TrueCrypt then makes the whole partition read-only until a remount.
Now this makes sense for a filesystem you're not using much - for example just storing some decoy files and afterwards adding a hidden partition, leaving the decoy files untouched or as read-only. However, in order for it not to look suspicious, the decoy operating system should of course be used constantly for insensitive work - this is even suggested by the TrueCrypt documentation.
But actually using the outer system seems really bothersome, since use means there's going to be a lot of writing - even if the partition is dedicated for data storage. So I would expect conflicts happen quite often: Even if the hidden partition is rather small (150 MB), assuming the data is distributed randomly in the free space, even if there's a thousand times larger amount of free space (150 GB) there would statistically happen a conflict when writing even 1 MB file into the outer partition. (That is, if my math is correct...) Even if you have 1,5 TB, you'd need to remount after even 10 MB writing - which to me sounds like the outer file system is pretty unusable for regular work.
I expect I have misunderstood something, but I didn't catch it in the documentation. So the question is: Does using the decoy operating system regularly mean that you'll have to constanty unmount/remount after a write conflict, making any file copying a tedious task? Or is there some method for TrueCrypt to prevent this? What is this method?