daitss/core — Issue #587: collect-fixities problem? fixity failure reported after fixity success check (E20110227_AAAAAC)
Author: lydiam
Created: 2011-11-30 16:01:12+00:00
State: open

Collect-fixities appears to have erroneously reported and created fixity failure events for E20110227_AAAAAC, after the most recent disk-fixity job showed a fixity success.

The most recent entries from the daitss_db.daitss2.events table:

2407167 | fixity success | 2011-11-09 19:00:47-05 |

| N/A | E20110227_AAAAAC | info:fcla/daitss/storage-master/1.3.6
2699080 | fixity failure | 2011-11-10 04:47:20-05 | http://storage-master.fda.fcla.edu:70/packages/E20110227_AAAAAC checksum errors: DAITSS DB has SHA1 of 6c46c4ea9859550fc8f37fe96d0d2f422d585d76, but si
lo at http://silos.darchive.fcla.edu:70/040/data/E20110227_AAAAAC reports da39a3ee5e6b4b0d3255bfef95601890afd80709 DAITSS DB has MD5 of f39d0300021fb0a7d703f7ce716a68bf, but silo at http://silos.darchive.fcla.edu
:70/040/data/E20110227_AAAAAC reports d41d8cd98f00b204e9800998ecf8427e | N/A | E20110227_AAAAAC | info:fcla/daitss/storage-master/1.
3.6
2701305 | fixity failure | 2011-11-11 05:20:47-05 | http://storage-master.fda.fcla.edu:70/packages/E20110227_AAAAAC checksum errors: DAITSS DB has SHA1 of 6c46c4ea9859550fc8f37fe96d0d2f422d585d76, but si
lo at http://silos.darchive.fcla.edu:70/040/data/E20110227_AAAAAC reports da39a3ee5e6b4b0d3255bfef95601890afd80709 DAITSS DB has MD5 of f39d0300021fb0a7d703f7ce716a68bf, but silo at http://silos.darchive.fcla.edu
:70/040/data/E20110227_AAAAAC reports d41d8cd98f00b204e9800998ecf8427e | N/A | E20110227_AAAAAC |info:fcla/daitss/storage-master/1.3.6
2703601 | fixity failure | 2011-11-12 04:43:12-05 | http://storage-master.fda.fcla.edu:70/packages/E20110227_AAAAAC checksum errors: DAITSS DB has SHA1 of 6c46c4ea9859550fc8f37fe96d0d2f422d585d76, but si
lo at http://silos.darchive.fcla.edu:70/040/data/E20110227_AAAAAC reports da39a3ee5e6b4b0d3255bfef95601890afd80709 DAITSS DB has MD5 of f39d0300021fb0a7d703f7ce716a68bf, but silo at http://silos.darchive.fcla.edu
:70/040/data/E20110227_AAAAAC reports d41d8cd98f00b204e9800998ecf8427e | N/A | E20110227_AAAAAC | info:fcla/daitss/storage-master/1.3.6

From the fixity.xml from silo /040 on tarchive:

From the fixity.xml from silo /040 on darchive:

Questions:

1. Why was fixity success recorded on 11/09/11 when the darchive silo fixity status at that time was presumably a failure?
2. Why didn't collect-fixities record a fixity success event in daitss2.events after the darchive tape silo's successful fixity check?

Collect-fixities needs to record a fixity success timestamped after 2011-11-12 before I feel comfortable withdrawing this AIP.

This AIP is in the batch of UF duplicates to be withdrawn and needs to be reconciled.