On Saturday 20 July 2002 10:39 pm, Peter Osterlund wrote:
Did you always see only 0's in the corrupted data? I remember I saw pieces from other files and seemingly random data.
Peter, I said I would do some more tests and I have done so. Not sure how much it helps but this is what I observe. Using the test I described in my message yesterday: 17 files were corrupted. In all cases, data had been replaced by 0's. 11 of the files had their first 2048 bytes set to 0 and of these 3 had second chunks of corruption. One, which was 3337 bytes in size, had the remainder of the file also set to 0 (i.e. it was all 0's). the other 2 had their final chunks, one starting at 0x6800 and the other at 0x1800, set to 0's. 5 files had their final chunks, starting at 0x1000, filled with 0's. 1 file had its final chunk, starting at 0x2000, filled with 0's. From these tests it would appear that it is always the first and final chunks of the file which are corrupted and sometimes it's both. The corruption always starts on a 2048 byte boundary, but I think we already knew that. From some notes I have from earlier tests, I can say for sure that different files are corrupted on each test I've kept the hexdumps of the pre and post copied files and the diffs from those hexdumps, and can tar them and put them in some free webspace for retrieval if they would be of any use to anyone. Also, more than happy to try any other tests that might be useful. Regards, Chris