Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

json has no hashsum? #462

Closed
ghost opened this issue Jan 4, 2021 · 4 comments
Closed

json has no hashsum? #462

ghost opened this issue Jan 4, 2021 · 4 comments
Labels

Comments

@ghost
Copy link

ghost commented Jan 4, 2021

I am trying to deduplicate remote disks, in a way that is suggested by issues #329 and #199

I'm running time rmlint -g -c json:unique -mkr // /home/.
When I am browsing the resulting json, I see no field for a hash sum. How would rmlint on a different machine, using --replay, find duplicates?

@ghost ghost changed the title json has not hashsum? json has no hashsum? Jan 4, 2021
@SeeSpotRun
Copy link
Collaborator

Yes, in the interest of execution time we don't complete checksums on files which diverge in the first few kb or so. Could add an option -c json:hash_uniques as a work-around if you still need this.

@SeeSpotRun
Copy link
Collaborator

Ok @lockywolf , two new options have now been added and merged into the develop branch https://github.com/sahib/rmlint/tree/develop.
With --hash-uniques, all found files get hashed.
With --hash-unmatched, only size-twins get hashed. This is more efficient for dupe-finding, because if you only have one file that is 4,635,235,654 bytes long then it can't have any duplicates.

Also with either of these options specified, you no longer need -c json:unique

@ghost
Copy link
Author

ghost commented Mar 22, 2021

That's going to help, thank you!

Shall the issue be closed?

@SeeSpotRun
Copy link
Collaborator

Resolved by #479.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant