`garage block info` can't be used with short block has from logs #682

New issue

Closed

opened 2024-01-05 12:49:48 +00:00 by zdenek.crha · 0 comments

zdenek.crha commented

2024-01-05 12:49:48 +00:00

Contributor

Description

The garage logs contains many messages related to block hashes, but seems to use a prefix of hash instead of full one. Trying to use this shortened hash in other garage commands like block info ends

Actual Outcome

# garage block info 305732a06f543471
Error: invalid hash

Expected Outcome

The command should be able to find block hash with given short prefix and either:

show block info
show list of block hashes sharing prefix and let user decide which to use

Motivation

First, I have been investigating resync errors and I could not use the block hash from logs for garage block info command. I had to use block list-errors, grep it for prefix from logs and use that which is not very user-friendly.

Second, in case the block hash is logged and it is not related to an error, it is impossible to get full hash and use garage block info to see where is it used.

## Description The garage logs contains many messages related to block hashes, but seems to use a prefix of hash instead of full one. Trying to use this shortened hash in other garage commands like `block info` ends ## Actual Outcome ``` # garage block info 305732a06f543471 Error: invalid hash ``` ## Expected Outcome The command should be able to find block hash with given short prefix and either: - show block info - show list of block hashes sharing prefix and let user decide which to use ## Motivation First, I have been investigating resync errors and I could not use the block hash from logs for `garage block info` command. I had to use `block list-errors`, grep it for prefix from logs and use that which is not very user-friendly. Second, in case the block hash is logged and it is not related to an error, it is impossible to get full hash and use `garage block info` to see where is it used.