I recently started playing around with Truecrypt however, I am having a rather interesting problem. Before Truecrypt, I was using Loop-AES with a 2 GB
container for my home directory. I never had any problems writing to the filesystem; worked pretty flawlessly so far as I could tell. Once I created my 2 GB Truecrypt volume and started
writing to it, that's where it got interesting. I found that at times I could mke2fs /dev/mapper/truecrypt0, other times mke2fs would hang on 'writing superblock accounting information'. Once
I finally got the container formatted and tried to cp my 948 MB home directory to the mount point of the volume, I ebserved on another console that the cp process abruptly died. My only
recourse after that was to reboot my laptop to get rid of the dead process, since even attempting to truecrypt -d would hang yet another console. Has anyone had this problem using
Truecrypt-4.2? I am also still on Linux-2.6.11.7 with compiled in device mapper support. If it helps, dmsetup --version says:
Library version: 1.01.05 (2005-09-26)
Driver version: 4.4.0
Does anyone know if this is a problem with Truecrypt, the device mapper, or perhaps both? Thanks.
container for my home directory. I never had any problems writing to the filesystem; worked pretty flawlessly so far as I could tell. Once I created my 2 GB Truecrypt volume and started
writing to it, that's where it got interesting. I found that at times I could mke2fs /dev/mapper/truecrypt0, other times mke2fs would hang on 'writing superblock accounting information'. Once
I finally got the container formatted and tried to cp my 948 MB home directory to the mount point of the volume, I ebserved on another console that the cp process abruptly died. My only
recourse after that was to reboot my laptop to get rid of the dead process, since even attempting to truecrypt -d would hang yet another console. Has anyone had this problem using
Truecrypt-4.2? I am also still on Linux-2.6.11.7 with compiled in device mapper support. If it helps, dmsetup --version says:
Library version: 1.01.05 (2005-09-26)
Driver version: 4.4.0
Does anyone know if this is a problem with Truecrypt, the device mapper, or perhaps both? Thanks.
