Bitcoin Forum

Bitcoin => Development & Technical Discussion => Topic started by: chalkboard17 on June 08, 2015, 08:22:41 PM



Title: Blockchain redownload after crash
Post by: chalkboard17 on June 08, 2015, 08:22:41 PM
Everytime my computer crashes/reboots while Bitcoin is still running, I have to redownload the entire blockchain again. I believe this demotivates people to run nodes. I suggest this to be fixed so people can run more nodes since it takes a long time to download and process entire blockchain. Perhaps doing backups from time to time, automatically, would be a good idea.


Title: Re: Blockchain redownload after crash
Post by: lemipawa on June 08, 2015, 08:38:28 PM
This actually happens to me also. You aren't redownloading the blockchain, you are reindexing the database. Since the LevelDB database is open when the node is running, if the computer crashes, the database is still open, and thus becomes corrupted. Once the database is corrupted, the node must rebuild it.

If your computer is constantly crashing, you should get that checked out. It usually means a hardware issue.


Title: Re: Blockchain redownload after crash
Post by: 2112 on June 08, 2015, 08:46:46 PM
It is probably not a whole re-download but just a re-build of the "chainstate" subdirectory. Keep a local backup of that directory that is periodically updated (I use 7-zip 'synchronize' option) and you should be fine.

On a parallel note: keep track of the people who say that "LevelDB" is a fuly ACID database engine and people who claim that Litecoin isn't meaningfully improving over the Bitcoin code. W.r.t. this bug this is a way to recognize liars and bullshit artists.


Title: Re: Blockchain redownload after crash
Post by: chalkboard17 on June 08, 2015, 10:17:59 PM
I am running Windows 10, since it's beta I get some crashes eventually (I'd say once every two days).
Thank you for the suggestion, coincidentally I thought of doing that after my last reboot. Hope it works out good.

I created this thread to make people aware of this problem, not for me, but for people who want to run nodes and might find this annoying. Nodes are always welcomed. This resync takes nearly 12 hours on my fast computer.


Title: Re: Blockchain redownload after crash
Post by: unamis76 on June 09, 2015, 12:11:26 AM
I am running Windows 10, since it's beta I get some crashes eventually (I'd say once every two days).
Thank you for the suggestion, coincidentally I thought of doing that after my last reboot. Hope it works out good.

I created this thread to make people aware of this problem, not for me, but for people who want to run nodes and might find this annoying. Nodes are always welcomed. This resync takes nearly 12 hours on my fast computer.

Crashes are rare on stable and fine tuned systems... Probably a good idea to switch OS if you want to run a node without any problems :)


Title: Re: Blockchain redownload after crash
Post by: 2112 on June 09, 2015, 01:00:00 AM
I am running Windows 10, since it's beta I get some crashes eventually (I'd say once every two days).
Thank you for the suggestion, coincidentally I thought of doing that after my last reboot. Hope it works out good.
You have some sort of problem with your hardware or configuration. While I don't run Win X, my friends are running the MSDN copy and it is running the cryptocoin daemons without any problems for much longer than what you see.


Title: Re: Blockchain redownload after crash
Post by: chalkboard17 on June 09, 2015, 01:05:26 AM
I am not worried about myself. I just thought this would be yet another reason for people not to run full nodes in general.


Title: Re: Blockchain redownload after crash
Post by: dogie on June 09, 2015, 01:12:16 AM
I am running Windows 10, since it's beta I get some crashes eventually (I'd say once every two days).
Thank you for the suggestion, coincidentally I thought of doing that after my last reboot. Hope it works out good.

I created this thread to make people aware of this problem, not for me, but for people who want to run nodes and might find this annoying. Nodes are always welcomed. This resync takes nearly 12 hours on my fast computer.

Crashes are rare on stable and fine tuned systems... Probably a good idea to switch OS if you want to run a node without any problems :)

I don't think I've ever unexpectedly restarted or turned off in the last 2 years of this Windows 8 build. I've black screened many a time, but it seems to still be able to shut itself down. Saying that, I too have also had to reindex a few times recently without unusual shutdowns or crashes. Is it possible there was a bug introduced?