Checking data integrity
Learn how to verify local files against .torrent files using the mkbrr check command
The mkbrr check
command verifies if the local files or directory match the data defined in a .torrent
file. This is useful for confirming the integrity of downloaded content or checking files after moving them.
Arguments
Required command arguments
Flags
Available verification options
Output
Understanding verification results
Examples
Common usage examples
Arguments
The path to the .torrent
file containing the expected piece hashes.
The path to the local file or directory containing the data to be checked.
The command exits with an error code if verification fails (bad pieces > 0 or missing files > 0).
Flags
Be verbose.
When enabled, shows detailed information about the verification process including any bad piece indices.
Enable quiet mode, printing only the final torrent file path upon success. Useful for scripts.
Useful for automated scripts or when you only need the verification status.
Manually specify the number of concurrent goroutines used for hashing.
Experimenting with different worker values might yield better performance than the default automatic setting.
Output
By default, the command provides a summary including:
- Completion: Percentage of pieces successfully verified against the local data.
- Good pieces: Number of pieces that match the hash in the torrent file.
- Bad pieces: Number of pieces where the local data hash does not match the torrent file.
- Missing files: Lists any files specified in the torrent that are missing locally. Files that exist but have an incorrect size will be listed with
(size mismatch)
appended to their name. - Check time: Duration of the verification process.
Examples
Check a downloaded directory:
Check a single file:
Check a downloaded directory:
Check a single file:
Check with verbose output to see bad piece indices:
Check in quiet mode for scripting:
Was this page helpful?