52
votes
Accepted
When should I use -reindex-chainstate and when -reindex
-reindex:
wipes the chainstate (the UTXO set)
wipes the block index (the database with information about which block is where on disk)
rebuilds the block index (by going over all blk*.dat files, and ...
11
votes
Accepted
Bitcoin Core - Go back to a specific block?
You can't delete the block data themselves, but you can reset the blockchain state to a specific block by using the invalidateblock command. This command will mark a specific block and its descendants ...
10
votes
Bitcoind, change to txindex=1
I would like to know, if using txindex = 1, will solve my problem with transactions that are not found.
Yes, getrawtransaction only works for transactions with unspent outputs, unless txindex is ...
9
votes
Accepted
How much extra disk space does txindex=1 require?
The total extra size is around 27GB as of June 2020. You can check by looking at the size of the $DATADIR/blocks/index directory.
If you copy that directory, you'll copy the index with it.
Historic ...
7
votes
Accepted
Can bitcoin core verify a third party blockchain download?
If you give Bitcoin Core a fully populated data directory, it will use it without any validation.
However, if you only give it the blocks/ subdirectory, it will fully validate it to recreate the ...
4
votes
Accepted
Which blk*.dat file contains a particular block?
Is there a way to find out which blk*.dat file contains a particular block?
We can't tell you which of your *.dat files contains block 478558 because there is no requirement that different nodes ...
4
votes
Accepted
Can I use blockfilterindex in pruned mode?
The block filter index is build asynchronously from block downloading and validation. It is possible that the thread handing block storage and pruning could be enough ahead of the thread building the ...
3
votes
Accepted
does Bitcoin Core automatically use reindex when you specify txindex=1 with existing sync'd chain?
Changing the txindex setting no longer requires a reindex since version 0.17.0 (see https://bitcoincore.org/en/releases/0.17.0/, under "Transaction index changes). It'll update just the txindex ...
3
votes
Accepted
Is txindex=1 necessary in the latest versions?
getrawtransaction's behaviour has not changed since Bitcoin Core 0.8 (up until at least 0.14).
It will always work:
For mempool (unconfirmed) transactions
For confirmed transactions that have ...
3
votes
Bitcoind --reindex vs starting allover again
bitcoind --reindex will be faster because starting over from scratch would not only do all the work bitcoind --reindex is doing, but it'd also have to go out and re-download all those blocks too.
3
votes
Accepted
If I am on a fork, can the reindex parameter fix this?
No, it would not. --reindex only handles the data that is stored on disk. Blocks are stored in the order that they are received, which is what brought you to your current view of the blockchain. So ...
3
votes
Does bitcoind ERROR "Disk space is too low!" refer to RAM or actual harddrive?
It refers to actual disk space. RAM is memory, not storage. The term "disk space" is very specific.
Then a while later this:
[2020-01-20T09:05:59Z Reindexing finished]
But bitcoind continued ...
2
votes
Accepted
Fixing "Block not found on disk" rpc error
Blocks are not stored in individual files, but flat bundles of a fixed size, so replacing one that is missing isn’t really possible. If a block can not be found on disk it has either keen deleted ...
2
votes
Accepted
Issue with getrawtransaction txindex and reindex
txindex=1 has to be added in the bitcoin.conf file.
When starting the node, the following command should be issued
bitcoind -reindex=1 -daemon
You can keep checking the debug.log file in the ....
2
votes
Accepted
Does bitcoind re-index or reverify downloaded blocks upon startup?
It walks back a small number of blocks and re-verifies them, this ensures there's no obvious corruption and warms the cache. It takes a few tens of seconds at maximum on most hardware. You can adjust ...
2
votes
Accepted
Shutdown bitcoin-qt during reindexing?
Can I safely shutdown and restart?
Yes.
If yes how? Do I have to pass --reindex again or will bitcoin-qt remember and continue from where it stopped?
No, Bitcoin Core will remember that it was ...
2
votes
Re-index/Re-download from specific height?
A reindex will not redownload the block. However, after safely shutting down Bitcoin Core, you can delete the block file containing that block. When you start it again, you will need to reindex, but ...
1
vote
How can I -abort ./bitcoind -reindex-chainstate?
-reindex-chainstate is an instant operation: it wipes a the chainstate (UTXO) database. It is performed at startup whenever the -reindex-chainstate command-line option, or the reindex-chainstate=1 ...
1
vote
Accepted
Why is the rate of reindexing chainstate not constant?
Updates to the UTXO are write cached, you will see pauses when this is flushed to disk periodically.
1
vote
`reindex-chainstate` configuration in bitcoin.conf?
Yes. All command line options can be specified in the bitcoin.conf file using the same name without the leading dash (-). For -reindex-chainstate, you add reindex-chainstate=1 to your bitcoin.conf.
1
vote
Bitcoin Core 'unable to open file' causes reindexing to fail
An exhaustive survey of Google searches relating to the failure to read blknnnn.dat files implicated data corruption on the hard drive or in files such as wallet.dat and/or blknnnn.dat. In my case, ...
1
vote
Txindex=1: how to recognise the blockchain with this option?
You can check the debug logs (might require -debug flag) and see if it is indexing transactions:
$ tail -f ~/.bitcoin/debug.log
You can also try to get a transaction by txid, and if it returns ...
1
vote
How long to -reindex -dbcache=2048 with txindex = 1?
I can make new address and send bitcoin in proccess of reindex?
Yes, but your wallet won't be able to check whether it has been confirmed by the network (i.e. mined) until it is caught up and synced ...
1
vote
How much extra disk space does txindex=1 require?
I just reindexed after setting txindex=1. My data directory increased in size about 3GB, but it seems like it might be saving data in another location since moving the data directory to other nodes is ...
Only top scored, non community-wiki answers of a minimum length are eligible
Related Tags
reindex × 37bitcoin-core × 17
bitcoind × 12
synchronization × 9
txindex × 5
block × 4
error × 3
blockchain × 2
blockchain-fork × 2
full-node × 2
pruning × 2
raspberry-pi × 2
json-rpc × 1
client × 1
bitcoin-cli × 1
balance × 1
armory × 1
raw-data × 1
peers × 1
bitcoin.conf × 1
sidechains × 1
leveldb × 1
block-validity × 1
storage-footprint × 1
bandwidth × 1