i have similar problems with my luks/dm-crypt encrypted partitions. using kernel 2.6.18, ubuntu 6.06 and encrypted my disks using the standard encryption method of luks. (cipher name: aes, cipher mode: cbc-essiv:sha256, hash spec sha1) filesystem is always ext3. when i used the standard kernel of ubuntu (2.6.15) i got a lot of "trying to access beyond end of device" errors in my syslog. with 2.6.18 this doesn't seem to happen anymore, but i still get file corruption when there's a lot of filesystem activity. for example if i try to compile a kernel on an encrypted partition, it will _always_ fail during the make process because some file got corrupted. when i compile the kernel on a non-encrypted partition, it will work without any problems. or when i copy a 1,6gb file from my windows machine to an encrypted partition over the network, the file will be corrupted. when i split the file into 30mb sized rar archives and copy it over, there will be lots of files with crc errors during unpacking. when i copy them to an unencrypted share and unpack there, everything works without problems. when i create a copy of the 1,6gb file on the same partition, "cksum" will show different checksums. smaller files will have the same checksum, when i copy them. i've tested this on partitions sized 20gb / over 150gb. i don't think that this is a hardware error, because it only happens on encrypted partitions. in some days i'll know for sure (buying new hardware). hardware at the moment: athlon 1200, 384mb ram (+encrypted swap), via ide chipset, new seagate 320gb harddisk (happened on a 200gb wd, too) --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
