Bitcoin Forum
December 17, 2017, 01:07:36 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Core: data consistency after forced exit during startup?  (Read 202 times)
jnano
Member
**
Offline Offline

Activity: 70


View Profile
November 23, 2017, 10:02:57 PM
 #1

I started Core by mistake with an empty "chainstate" directory, after it was fully synced the last time it ran.

The startup window stopped making progress at "Pruning blockstore". I tried to exit it normally. The shutdown popup window appeared ("Bitcoin Core is shutting down...") but it never progressed, so I killed the process.

The chainstate directory held 4 files: *.log, CURRENT, LOCK, and MANIFEST-*.
If I'm not mistaken the files under "blocks" weren't touched, based on file time.

I restored the chainstate directory data and restarted the software. It loaded normally.
Can I be sure all data is fine?
1513516056
Hero Member
*
Offline Offline

Posts: 1513516056

View Profile Personal Message (Offline)

Ignore
1513516056
Reply with quote  #2

1513516056
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1513516056
Hero Member
*
Offline Offline

Posts: 1513516056

View Profile Personal Message (Offline)

Ignore
1513516056
Reply with quote  #2

1513516056
Report to moderator
BitMaxz
Hero Member
*****
Offline Offline

Activity: 910


View Profile
November 23, 2017, 11:54:17 PM
 #2

If its fully synced it would not be  a problem to test try to send small amount of bitcoin core address but first backup your private keys from bitcoin core.. before sending small amount of bitcoin for testing purposes if  its not working fine  try this command -rescan .. and check your blocks if all are downloaded use this command -checkblocks But its should be automatically check your blocks if its up-to-date.
you may also reindex chainstate
Code:
-reindex-chainstate Rebuild chain state from the currently indexed blocks
-reindex Rebuild chain state and block index from the blk*.dat files on disk
You can see the other command check the source below..

Source: https://en.bitcoin.it/wiki/Running_Bitcoin

jnano
Member
**
Offline Offline

Activity: 70


View Profile
November 24, 2017, 02:05:53 AM
 #3

Thanks.

It's in pruned mode, so no full blockchain. By fully synced I just meant that on the last run it didn't have any remaining catching up to do, and the chainstate directory was fully populated (it was empty on the next run because I temporarily moved it).

I assume it's meant to survive abnormal shutdowns, plus it does check some or more of the data on startup. Additionally, the abnormal run didn't even finish the startup phase, so I think it was before any important writing action.

Everything looks fine, just wanted to know if looks can be deceiving. Smiley


Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!