I am experiencing kernel panic when trying to mount a ext4 filesystem which itself resides on a truecrypt volume mounted using
-m nokernelcrypto option.
The system is CentOS 6.3, OpenVZ Kernel 2.6.32-042stab074.10
The disk is a virtual disk (a truecrypt volume mounted with
--filesystem=none), and the actual command triggering kernel panic is:
mount -o loop -t ext4 /tmp/.truecrypt_aux_mnt2/volume /mnt/storage
- It mounts fine in read-only mode, i. e. using
- It also mounts perfectly fine if I boot in "normal" kernel (non-OpenVZ), which is 2.6.32-279.22.1.el6.x86_64
- Again, it mounts perfectly fine when not using
-m nokernelcrypto(either kernel)
- I have to use
-m nokernelcryptobecause a 3TB disk that I have can only be mounted using that option — otherwise truecrypt refuses to mount saying "Kernel cryptographic service test failed" and suggests to upgrade kernel to 2.6.33. Not using
-m nokernelcryptogoes OK with 2TB disks, but not with 3TB
- The panic message features "Kernel panic - not syncing: Fatal exception" and "kernel BUG at fs/fuse/file.c:1110!"
- I did not have this problem when I was using Debian OpenVZ — was able to mount the 3TB using
I am just not sure where exactly the problem is: CentOS, OpenVZ, fuse library or the non-kernel decryption. Any clues will be much appreciated.