Was testing on a VM with less space than I expected. Node cleanly shutdown due to disk space low, but after resizing disk larger and restarting, it insisted on a reindex.
-prune=550
Running out of disk space forces pruned node to reindex #18301
issue luke-jr opened this issue on March 9, 2020-
luke-jr commented at 4:09 PM on March 9, 2020: member
- luke-jr added the label Bug on Mar 9, 2020
-
MarcoFalke commented at 4:19 PM on March 9, 2020: member
What is the error message that prompts the reindex?
checkblock,leveldb, ... ? -
emilengler commented at 11:37 AM on April 1, 2020: contributor
I'm currently trying to reproduce, what does prune option mean? Have you executed it after you resized your disk or was your node running the entire time with
-prune=550? -
luke-jr commented at 12:32 PM on April 1, 2020: member
It was
-prune=550the entire time. After the clean out-of-space shutdown, the VM itself was rebooted to make the virtual disk larger. -
MarcoFalke commented at 11:52 AM on February 8, 2021: member
Duplicate of #17392 ?
-
- fanquake closed this on Aug 9, 2022
- bitcoin locked this on Aug 9, 2023
Contributors
Labels