feat: add --store-hash to ltfs_ordered_copy tool to store content hashes in ltfs.hash.* VEAs when destination is ltfs#602
Open
hugo-hur wants to merge 2 commits into
Open
Conversation
Author
|
Noticed that there is actually limitation in the format spec what hashes can be used and in what format even though the implementation does not enforce it. Now the hashes should be standard conforming. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of changes
This pull request includes following changes or fixes.
Description
I thought that this feature could be useful for some archival situations that I'm running to add strong file level verification.
Since LTFS 2.4. version there is dedicated spot for these content hashes in the xattrs so why would not use those.
Tested with python 2.7 and 3+
Type of change
Checklist: