the prometheus cat not reboot and raise error: opening storage failed: reloadBlocks: corrupted block 01HWG13YX2E4S0BPKH52V2W2SY: invalid magic number 7b0a0922
What did you expect to see?
prometheus can reboot normally.
What did you see instead? Under which circumstances?
prometheus CrashLoopBackOff, and I query it's logs and see error: opening storage failed: reloadBlocks: corrupted block 01HWG13YX2E4S0BPKH52V2W2SY: invalid magic number 7b0a0922
I see the block in question is 01HWG13YX2E4S0BPKH52V2W2SY, However, in the above log, this block
It's healthy. I can see the logs are:
But when I went to the node to check the block information, I found that the ulib in the meta.json of this block is inconsistent with the name of the directory:
So why the dir name is 01HYD63XFEZ2HP3037ZD49NKF5 ,but meta.json ulib is 01HWG13YX2E4S0BPKH52V2W2SY? I think this is what caused the prometheus reboot to fail.
Does Prometheus allow this, or is it a bug?
What did you do?
the prometheus cat not reboot and raise error: opening storage failed: reloadBlocks: corrupted block 01HWG13YX2E4S0BPKH52V2W2SY: invalid magic number 7b0a0922
What did you expect to see?
prometheus can reboot normally.
What did you see instead? Under which circumstances?
prometheus CrashLoopBackOff, and I query it's logs and see error:
opening storage failed: reloadBlocks: corrupted block 01HWG13YX2E4S0BPKH52V2W2SY: invalid magic number 7b0a0922
I see the block in question is 01HWG13YX2E4S0BPKH52V2W2SY, However, in the above log, this block It's healthy. I can see the logs are:
But when I went to the node to check the block information, I found that the ulib in the meta.json of this block is inconsistent with the name of the directory:
So why the dir name is 01HYD63XFEZ2HP3037ZD49NKF5 ,but meta.json ulib is 01HWG13YX2E4S0BPKH52V2W2SY? I think this is what caused the prometheus reboot to fail. Does Prometheus allow this, or is it a bug?
System information
No response
Prometheus version
Prometheus configuration file
No response
Alertmanager version
No response
Alertmanager configuration file
No response
Logs