It means that an eyeball of the contents of the files shows obvious differences. And in the case of some of the shared tarballs, the file structure isn't even recognized as TAR format on the client, although it works just file on the server.
Almost everything on the shares is binary, so I don't have any text files long enough to exhibit selective corruption. On Wed, 2012-07-18 at 18:09 +0000, Allen, Tom (GE Transportation) wrote: > What does corrupt mean in this case? Non-matching md5sums or some sort of > recognizable error? And when you say "binary files" do you mean this > doesn't affect plain text files? Have you verified that last bit with MD5? > > --------------------------------------------------------------------- Archive http://marc.info/?l=jaxlug-list&r=1&w=2 RSS Feed http://www.mail-archive.com/[email protected]/maillist.xml Unsubscribe [email protected]
