On 09/03/2010 03:21 PM, Thorsten Peter wrote: > I am switching from loop-aes to dm_crypt. I am trying to use it on a > fresh Ubuntu 64bit server installation with my 6x750gb Software raid5 array. > Array is clean and freshly created, I encrypted it using > > cryptsetup -y -c aes -h ripemd160 -s 256 create STUFF /dev/md0 Please use LUKS instead here to get persistent header. > Format went fine, but when I try to copy back large amount of data to > the encrypted array (about 900gig) my copy thread always hangs itself at > some point during the process. I can't access the array anymore, though > the raid itself is fine, no drives are kicked out or anything. > Reboot gives me back access and the array is still ok. > When the problem occures I see the following trace in log: > > Aug 29 02:54:24 liberty24 kernel: [221558.020638] Pid: 400, comm: > md0_raid5 Not tainted 2.6.32-24-server #41-Ubuntu Unknow If it is reproducible with upstream kernel, please send me OOPs, if not, please use Ubuntu bugzilla - I saw strange reports which were never reproducible on upstream. (The bug seems like something we fixed long time ago.) Milan _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
