https://bugzilla.kernel.org/show_bug.cgi?id=15806
Summary: Kernel Panic or Kernel becomes unstable with encrypted
drives (TrueCrypt)
Product: File System
Version: 2.5
Kernel Version: linux kernel 2.6.34-999-generic (Ubuntu mainline
Kernel)
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: no-spam@spamfence.net
Regression: No
Created an attachment (id=26040)
--> (https://bugzilla.kernel.org/attachment.cgi?id=26040)
Includes kern.log, linux-image.crash-log and file with system information
* Overview: More detailed restatement of summary.
I have 2 encrypted drives, the Kernel becomes unstable or I get Kernel Panic
when I'm using one of this drives. This means, if I try to copy files from one
encrypted drive to another I get in the most cases Kernel Panic after a short
time.
If accessing more than one application files from an encrypted drive, I get
often the message that the system might become unstable and I need to reboot
because I can't access the encrypted drive any more. The same when I try to
force a file system check with fsck, I get every time the message that the
system might become unstable.
* Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the
bug. Include any special setup steps.
The easiest way to reproduce is to check the file system with fsck:
1) Mount the volume with the TrueCrypt GUI (check under "Filesystem: Do not
mount")
2) Force file check with "sudo fsck -f /dev/mapper/truecrypt1"
3) After a short while I get a new icon in the tray with the message "Your
system might become unstable now and might need to be restarted."
* Actual Results: What the application did after performing the above steps.
The Kernel becomes unstable (Your system ...
