Repository navigation
Checksum files after stashcp #29
Description
If CVMFS is accessible - but transfer from CVMFS fails - we should at least take advantage of the hash:
# attr -qg hash /cvmfs/nova.osgstorage.org/flux/g4numi/v6/me000z200i/g4numiv6_minervame_me000z200i_18_0006.root
aa1c8b1ef136647a082146a890b7e283f5e6a753
# sha1sum /cvmfs/nova.osgstorage.org/flux/g4numi/v6/me000z200i/g4numiv6_minervame_me000z200i_18_0006.root
aa1c8b1ef136647a082146a890b7e283f5e6a753 /cvmfs/nova.osgstorage.org/flux/g4numi/v6/me000z200i/g4numiv6_minervame_me000z200i_18_0006.root
After transferring with xrdcp, we should validate the checksum if it is available from CVMFS.
Activity
djw8605 commentedon Dec 6, 2016
I actually ran into a corner case for this.
xrdcp, it copied the correct file. But the Checksum in CVMFS would have been of the old one.Therefore, if a user tries to copy a file that has the same name as an old file, but with new content, then this test would fail. Matter of fact, if the transfer fails with CVMFS, but the file is in the CVMFS namespace, then we shouldn't trust CVMFS at all, it's likely it caught the same error.
bbockelm commentedon Dec 6, 2016
I think this at least merits a warning in stdout!