IntegrityChecker Java (icj): Suppressing Innocuous HASHES_MATCH_DATE_CHANGED Warnings

2022-01-03 • SEND FEEDBACK |
Related: data integrity, diglloydTools, IntegrityChecker, Java

re: IntegrityChecker Java
re: data integrity

Reader Tony V writes:

Would it be possible to configure icj to not inform about the change of dates ?

If I read the documentation correctly, it appears that I can only ignore a bundle formed of 'change of date' 'change of size' 'change of date+change of size' ... but I would basically like to ignore only 'change of date' for * (all files).

For example:

/Volumes/NO NAME/1.mp3 HASHES_MATCH_DATE_CHANGED stored "2022-01-02 17:01:25.360" now "2022-01-02 17:01:24.000" GMT-0 /Volumes/NO NAME/2.mp3 HASHES_MATCH_DATE_CHANGED stored "2022-01-02 17:01:31.950" now "2022-01-02 17:01:30.000" GMT-0

MPG: the warnings stem from the use of the FAT32 file system, which cannot capture dates the same way as macOS file system, hence the data change warnings. Other metadata is also lost by backing up to FAT32; in general backing macOS files up to a non-macOS file system is not an ideal solution (but it also won’t matter for most types of files).

One way to deal with the output is to remove strip-out the unwanted messages via grep:

icj verify ... | grep -v HASHES_MATCH_DATE_CHANGED

Example for Tony V

There is no global flag for suppressing these innocuous messages everywhere.

However, the [output.suppressInnocuousChanges] section of ~/.icj_prefs_customized preferences file can do so, although it also suppresses other innocuous messages (not just HASHES_MATCH_DATE_CHANGED).

The line shown in blue will suppress all such messages on the volume "NO NAME". In theory one could suppress the message on all volumes by using "/Volumes/**".

###############################################################################################################
[output.suppressInnocuousChanges]
###############################################################################################################
# Paths for folders or files for which innocuous change messages are suppressed.
# Auto-globbing: NO
# Innocuous changes are:  {SIZE_CHANGED, DATE_CHANGED, HASHES_MATCH_DATE_CHANGED, HASH_CHANGED_DATE_CHANGED}
# output of verbose or debug disables this feature.
/Volumes/NO NAME/**

Another example

Here is a more complete example, one I use myself.

###############################################################################################################
[output.suppressInnocuousChanges]
###############################################################################################################
# Paths for folders or files for which innocuous change messages are suppressed.
# Auto-globbing: NO
# Innocuous changes are:  {SIZE_CHANGED, HASHES_MATCH_DATE_CHANGED, HASH_CHANGED_DATE_CHANGED}
# output of verbose or debug disables this feature.
# noisy photo libraries
**.photoslibrary**
**.aplibrary**
**Previews.lrdata**
# suppress huge numbers of nuisance files caused by  Apple crapware 
**/Users/*/Library/**
# maven: suppress messages for build folders and repository changes
**/target/{classes,test-classes,surefire-reports,generated-sources,maven-archiver}**
**/.m2/**