Is it possible to configure hashdeep in audit mode to treat file duplicates differently than missing files? In particular, if hashdeep can confirm that a copy of the file is still found, mark it as something other than "Missing". Here's the scenario I'm trying to work through:
All the files have identical contents and hashes. When running an audit of the destination directory against a hash file from the originals directory, the audit log will correctly indicate that photoA.jpg was "moved" to myphoto.jpg, but will then indicate that photoA-1.jpg and photoA-2.jpg are "missing".
I understand the logic, but it seems that in some cases you would want to be able to say that both photoA-1.jpg and photoA-2.jpg were "moved" to myphoto.jpg, as would be the case if you were trying to deduplicate files. Is there a straightforward way to get audit to ignore or somehow flag these cases a different from a truly missing file?
Is it possible to configure
hashdeepin audit mode to treat file duplicates differently than missing files? In particular, ifhashdeepcan confirm that a copy of the file is still found, mark it as something other than "Missing". Here's the scenario I'm trying to work through:All the files have identical contents and hashes. When running an audit of the
destinationdirectory against a hash file from theoriginalsdirectory, the audit log will correctly indicate thatphotoA.jpgwas "moved" tomyphoto.jpg, but will then indicate thatphotoA-1.jpgandphotoA-2.jpgare "missing".I understand the logic, but it seems that in some cases you would want to be able to say that both
photoA-1.jpgandphotoA-2.jpgwere "moved" tomyphoto.jpg, as would be the case if you were trying to deduplicate files. Is there a straightforward way to get audit to ignore or somehow flag these cases a different from a truly missing file?