Zenon Panoussis wrote: > Alasdair G Kergon wrote: > >>> [root@njoerd lsat]# md5sum 006069_15meROT.tif >>> 0ce8093accb771c66a0154b4d55fd90b 006069_15meROT.tif >>> [root@njoerd lsat]# md5sum 006069_15meROT.tif >>> fc2caf002b693c1283a10536fa976358 006069_15meROT.tif > >> Compare two files carefully and analyse which bytes are actually >> corrupt. > > I cannot very well compare a file with itself, can I? That's what > I'm looking at above, one single file returning different checksums > every time. That makes rsync and the contents of the file on the > other computer completely irrelevant. If we forget rsync and assume > that the file was created on this machine, the problem is still there. md5sum tool computes the md5 sum by reading the entire file. Copy the same file to /root/fileA and then to /root/fileB. That should create two different files. Then compare files in /root. Henrik Holst --------------------------------------------------------------------- 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
