option to rehash on change of ctime vs mtime

[patrickwolf]

When a file is deduplicated (#15 ) its size and mtime does not change. So hashio would not know that deduplication has occurred
In general that is fine since deduplication should not change the file data...

But in my case I'd like to make a snapshot before deduplication and also make one after deduplication and I would like for a new hash to be generated so I can verify 100% that nothing has changed.

For this use case to work a new option would be needed --verify-ctime and if this option is set and the ctime has changed then the file would need to be rehashed even if mtime has not changed.

Alternatively in case this is too specific an option --rehash or --ignore-cache would be helpful that allow for rehashing for those that are paranoid or need 150% certainty.

[rsgalloway]

When a file is deduplicated (#15 ) its size and mtime does not change

interesting.

mtime is hardcoded, but I could expose it as an arg, or a config option.

Alternatively in case this is too specific an option --rehash or --ignore-cache would be helpful that allow for rehashing for those that are paranoid or need 150% certainty

does --force/-f work for you? it will force a recache. the only issue is that it will also hash ignorable files, but at least you can verify the hash values.

another option would be to use two different cache files:

$ HASHIO_DB=./db1.sql hashio <PATH> -v -o hash1.json
$ HASHIO_DB=./db2.sql hashio <PATH> -v -o hash2.json
$ hashio --verify hash1.json hash2.json

[patrickwolf]

I imagine what would work best is similar to -v -v if we had -f -f
-f rehash files but not ignorable
-ff rehash files and ignorables

and cool that the 2 DB and external hash file solution would work. You build a great command line API here

[rsgalloway]

this is a great idea, will try to get it into the next release.

You build a great command line API here

thanks!