Hello all Running rsync -vvac I kept getting checksum mismatches. Trying to isolate the cause, I was faced with this: [root@njoerd lsat]# md5sum 006069_15meROT.tif 0ce8093accb771c66a0154b4d55fd90b 006069_15meROT.tif [root@njoerd lsat]# md5sum 006069_15meROT.tif fc2caf002b693c1283a10536fa976358 006069_15meROT.tif [root@njoerd lsat]# md5sum 006069_15meROT.tif 9ff9da9e1759caa50a5145b668ef9231 006069_15meROT.tif [root@njoerd lsat]# mv 006069_15meROT.tif /root/ [root@njoerd lsat]# cd /root/ [root@njoerd ~]# md5sum 006069_15meROT.tif 80ff8ae8dc281288ec2ece20f9d4087a 006069_15meROT.tif [root@njoerd ~]# md5sum 006069_15meROT.tif 80ff8ae8dc281288ec2ece20f9d4087a 006069_15meROT.tif [root@njoerd ~]# md5sum 006069_15meROT.tif 80ff8ae8dc281288ec2ece20f9d4087a 006069_15meROT.tif The directories lsat and root are on the same drive, on different partitions. lsat is encrypted with dm-crypt (twofish), root is not. I've tested the RAM as best I could and it seems to be good. fsck reports "all well" and the problem manifests itself anywhere on the partition, not in any one specific place. This happens all the time and it only happens with big files. For instance, this tiff is 680 MB. The system is centos 4.3 running kernel 2.6.9-34.0.2.EL (with redhat backporting things kernel versions mean very little, but at least it's surely newer than 2.6.4-rc2). Could it be dm-crypt glitching? Has anyone seen anything similar? In about two years of routinely using dm-crypt I've never had file corruption or any similar oddities before. Then again, I don't know what else I could blame for the md5sum nuttiness above. Z --------------------------------------------------------------------- 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
