Truecrypt container suddently turns read-only
I have experienced a very inconvenient bug in TrueCrypt. The bug has been reported by several users at the TrueCrypt forum. After mounting a volume with TrueCrypt, when launching a (triggering) application the container suddenly becomes read-only. The effect repeats in 100% percent of cases and it remains happening at 5.0a and 6.0 whether you recompile the source or you use pre-compiled packages. The back-thirsted 4.3a version no longer appears to compile on the kernel.
The most irritating part of it is that for a long time the system functions correctly. I have a clue what may cause this and I am checking it out as I write this entry. I think the filesystem has been contaminated (this happens frequently on reiserfs), and when the driver returns an error the Fuse or TrueCrypt (I am not sure which) closes the write acces to protect the drive. If my conjecture is correct, than after the
fsck.reiserfs –rebuild tree
This bug will disappear. Even if this is a self-protection mechanism I still can’t understand why isn’t it reported in dmesg or in the truecrypt state log?
I use a via-epia en 1.5GHz, with OpenSUSE 11.0
update:
That was indeed the filesystem, which had to be checked. The driver probably returned an error and as protection mechanism the container became read-only. Whether it makes sense? maybe. How to switch this protection of? I don’t know.
If you had the same error and filesystem check didn’t work, than please leave a comment.