'tahoe debug verify-share' command #508

Open
opened 2008-09-03 01:33:54 +00:00 by warner · 0 comments

To assist with immutable-file repair, it would be useful to have a tool that you could point at a share file and it would tell you if all the internal hashes are valid. If you give it a URI too (a read- or verify- cap), then it should be able to compare the UEB hash against the one from the URI.

This should look like:

tahoe debug verify-share --uri URI:CHK:blah node*/storage/shares/ab/abcedSIetc/*
share 1: node1/storage/shares/ab/abSIetc/1 : all hashes good
share 4: node3/storage/shares/ab/abSTetc/4 : bad ciphertext tree hash
...
To assist with immutable-file repair, it would be useful to have a tool that you could point at a share file and it would tell you if all the internal hashes are valid. If you give it a URI too (a read- or verify- cap), then it should be able to compare the UEB hash against the one from the URI. This should look like: ``` tahoe debug verify-share --uri URI:CHK:blah node*/storage/shares/ab/abcedSIetc/* share 1: node1/storage/shares/ab/abSIetc/1 : all hashes good share 4: node3/storage/shares/ab/abSTetc/4 : bad ciphertext tree hash ... ```
warner added the
operational
minor
task
1.2.0
labels 2008-09-03 01:33:54 +00:00
warner added this to the undecided milestone 2008-09-03 01:33:54 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#508
No description provided.