hang-ups during Fixity audit?
Paul Dougherty
Hi,
I had been running Fixity from one Mac where I would find that in audit would seem to hang up for mysterious reasons. I have no way of looking under the hood, but the scan would appear to be humming along (flashing directories in the Scanner Console) but would go on for days beyond any reasonable length of time.
I’m writing this post today because the same apparent hang up has now happened on the second Mac, I was doing a ‘speed test’ hoping this second Mac (new MacBook) would run the audit much faster than on my iMac. However even though there don’t appear to be any network connection issues* the faster MacBook had already run for about 36 hours and was still churning away… whereas the original scan on the same target folder performed on the iMac only took 8 hours.
*We are working on an isolated 10G network. In the case of the MacBook hangup, we were connected directly into the QNAP 1685 10G port. Speaking of QNAP, I am not happy with their Hybrid Backup Sync reports (made with multi-versioning on). So that makes the Fixity reports all that more valuable to monitor changes in the archive… if only I could rely on them. (Besides the above problem, the audits are slower than I expected but granted I have little experience here.)
While not exactly the same as a hangup, which would imply the audit will never end, I do have this example below were the first pass took 54 hours, and the next one took less than 5 hours (same Mac). There were 3 target folders adding up to 1.3TB. I haven’t gained enough expertise to know what the duration ratio should be between the first scan and subsequent audits. (see below)
So in summary I guess I am posing two questions or a question in a feature request. I wish there was a better mechanism for monitoring progress other than the directory flashing by during a scan. This flashing activity in the Scanner Console has proven missed leading in so far is it implies progress but the scan is either stuck or endless.
The other question is more prosaic and involves a duration of the first audit versus a follow-up audit on a directory that has not changed much, should the scan duration be approximately the same? That would appear not to be the case as per these two summaries of an audit on the same folder made from the same Macintosh.
Thanks in advance for any suggestions.
Paul Dougherty
Video Archivist
International Rescue Committee
Fixity report
Project name Fixity_exp_ext_camp
Algorithm used sha256
Date 2018-08-27
Time Elapsed 54 hrs 8 min 47 seconds
Total Files 7885
Confirmed Files 0
Moved or Renamed Files 0
New Files 7885
Changed Files 0
Removed Files 0
Fixity report
Project name Fixity_exp_ext_camp
Algorithm used sha256
Date 2018-09-01
Time Elapsed 4 hrs 53 min 40 seconds
Total Files 7885
Confirmed Files 7540
Moved or Renamed Files 0
New Files 345
Changed Files 0
Removed Files 0
