We are attempting to run md5sum on the source and destination locations after migrating

from the CAS -> FMA - > NS80 (NS80 front-end) to the Isilon to check for possible corruptions

I have noticed that we are getting different checksums (md5) being generated for the same file

This issue seems to only happen on some files and is not consistent across all files.  I cannot

see any pattern in terms of size or anything else.

The issue also manifests when there is I/O in progress on the Centera and a checksum is taken

during the same time.

Again issue is not happening all the time, but maybe seen once in around 1000 files...

Because of the above we are getting a lot of md5 mismatches when running a compare but with no corruption seem on the destination......

I'm not sure whether the way the Centera is hydrating the files has anything to do with this at all?

md5 checking is enabled on the EMCopy flag but this hasn't proved reliable as there are files which have been copied with different checksums but Emcopy has not reported them

I'm not sure other customers have experienced this before but due to the sensitive data onsite a requirement

has been put into place to ensure integrity when migrating.  We have files on archive files going back 1995 and older

thanks