On my system I created a new truecrypt volume in a file called files.tc with: truecrypt -k NewKey -c files.tc The filesize is 200GB and then I tried formatting the volume with mkfs.ext2 /dev/mapper/truecrypt0 The process starts and in the middle of it the whole system hangs. No login, reset, etc. is possible. There are no messages in the log files or visible kernel panics. I repeated the procedure with a new container file, mkfs.reiserfs instead of mkfs.ext2 but it always halts the system. Accessing the file itself with dd, exporting over samba, etc. works fine, so I don't think it is a hardware flaw or a problem with the underlying filesystem (reiserfs v3). I updated my system a week ago and never had a problem with truecrypt 4.0 My system is running a 2.6.15-gentoo-r1 kernel with normal CFLAGS (-march=pentium2 -O2 -pipe -fomit-frame-pointer).
Created attachment 94613 [details] output of emerge --info
I am just curios... Have you tried the loop-aes alternative? I think it is much simpler.
I need a cross platform approach to encryption and loop-aes does not work together with WinXP, so yes, I have tried it but I consider truecrypt the better alternative in my case. As a workaround I formatted the volume with NTFS under WinXP and my gentoo box can read the files just fine, have not tried write support of NTFS under linux yet.
I understand. Have you tried to contact up-stream regarding this issue? I am just not sure that a fix for such problem is at Gentoo.
I have not contacted the truecrypt people yet. I can try to create a test case over the next weeks on another system because I don't want to always crash my file server. At the moment I don't know whether it is truecrypt or the mkfs utilities that are causing the trouble. Accessing the block device at /dev/mapper/truecrypt0 with dd worked fine so far, just creating a file system fails. I did not access the whole 200GB with dd, so maybe that makes the difference. So thanks for the feedback, I can't invest much time into this at the moment but I will report my progress here.
Thanks. I don't think it is mkfs, user mode usually won't cause such problems. It can be ext2, but again, it works great with all other backed devices. So my guess is that the truecrypt modules are incompatible. Can you please close this bug as RESOLVED-NEEDINFO, until you have more information regarding this, and reopen it when you have more information?
Creating test case to find cause of problem.
