Bitcoin Forum

Bitcoin => Development & Technical Discussion => Topic started by: joe1234 on December 02, 2017, 01:26:36 PM



Title: time to re-sync a powered-off fullnode
Post by: joe1234 on December 02, 2017, 01:26:36 PM
Hello forum


- does a fullnode after a power-outage (e.g. 24h) automatically re-sync?


- Does such re-sync entirely depend on the speed of my internet connection?



Thank your for your feedback!

Joe


Title: Re: time to re-sync a powered-off fullnode
Post by: ranochigo on December 02, 2017, 02:30:35 PM
- does a fullnode after a power-outage (e.g. 24h) automatically re-sync?
Depends. For Bitcoin Core, if your client gets shut down unexpectedly, your database might get corrupted. If that happens, you'll have to reindex the whole database which would take quite a while.
- Does such re-sync entirely depend on the speed of my internet connection?
No. It's mainly dependent on your processor and also the speed of your hard disk. It's the same with when your client gets synchronized the first time.


Title: Re: time to re-sync a powered-off fullnode
Post by: joe1234 on December 07, 2017, 05:38:25 PM
- does a fullnode after a power-outage (e.g. 24h) automatically re-sync?
Depends. For Bitcoin Core, if your client gets shut down unexpectedly, your database might get corrupted. If that happens, you'll have to reindex the whole database which would take quite a while.
Do you mean by "your client" e.g. my lightweight wallet?

Tahnk's a lot for any clarification!
Joe


Title: Re: time to re-sync a powered-off fullnode
Post by: HCP on December 08, 2017, 02:17:52 AM
Do you mean by "your client" e.g. my lightweight wallet?
No... he means your Bitcoin Core "Full node" client...

What he is saying... is that the syncing "speed" (in terms of blocks/second) of a node that was powered-off, will be similar as it was when it was first synced up after installation... it still needs to download and verify every block which requires processor power and harddrive speed for optimal performance.


Title: Re: time to re-sync a powered-off fullnode
Post by: Jet Cash on December 08, 2017, 09:24:22 AM
The core software seems to be well written and robust. I run a full node over public WiFi, and the sync speed seems to be influenced by the quality and speed of the network connecton, and the speed and availablity of peers. Of course you should always shut down correctly, but if you forget, then Core sems to be able to sort things out. As a safety precaution I always restart in an orderly fashion once it starts to resync following an instant shut down. If you have a bad block on the hard drive, you can copy the blockchain up to that point, and let Core resync from the good blocks. That can save you time in downloading.


Title: Re: time to re-sync a powered-off fullnode
Post by: btctousd81 on December 10, 2017, 01:33:06 AM
- does a fullnode after a power-outage (e.g. 24h) automatically re-sync?
Depends. For Bitcoin Core, if your client gets shut down unexpectedly, your database might get corrupted. If that happens, you'll have to reindex the whole database which would take quite a while.
- Does such re-sync entirely depend on the speed of my internet connection?
No. It's mainly dependent on your processor and also the speed of your hard disk. It's the same with when your client gets synchronized the first time.

doesnt block files get downloaded again ?

after unexpected power down of bitcoin-core ?

or it just rereads .blk files and creates chainstate db ? so no need to download blok files again.

Thanks


Title: Re: time to re-sync a powered-off fullnode
Post by: ranochigo on December 10, 2017, 02:53:09 AM
doesnt block files get downloaded again ?
after unexpected power down of bitcoin-core ?
or it just rereads .blk files and creates chainstate db ? so no need to download blok files again.
Thanks
If you're unlucky and your computer turns off abruptly while syncing, your chainstate might be corrupted and you will need to reindex the whole blockchain again. It does not need to download the blocks again though I had some success with it when reindex doesn't work.