After having finished the "Initial Block Download" I needed to reindex:

[BTC_Core_Expmnt]# bitcoind -reindex -datadir=/mnt/BTC_Core_Expmnt

The debug.log showed everything starting up ok; and the process beginning:

[2020-01-20T07:43:41Z Loaded 119369 blocks from external file in 6005ms\
2020-01-20T07:43:41Z Reindexing block file blk00001.dat...]

Then a while later this:

[2020-01-20T09:05:59Z Reindexing finished]

But bitcoind continued grinding on... Well then what is all this? ::

[2020-01-20T09:05:59Z Pre-allocating up to position 0x100000 in\
[rev00000.dat 2020-01-20T09:05:59Z UpdateTip: new best=\ 
[height=1 version=0x00000001 log2_work=33.000022 tx=2\
[date='2009-01-09T02:54:25Z' progress=0.000000 cache=0.0MiB(1txo)]

In any case it got to this point ::

[2020-01-20T09:59:00Z UpdateTip: new best=\
[height=359645 version=0x00000003 log2_work=82.893764 tx=71128141\
[date='2015-06-06T07:25:10Z' progress=0.143166\

Then it fell over ::

[2020-01-20T09:59:00Z *** Disk space is too low!
[2020-01-20T09:59:00Z Error: Disk space is too low!\
[Error: Disk space is too low!
[2020-01-20T09:59:00Z Failed to connect best block\
[ (Disk space is too low! (code 0)) ]

Which is odd, because there should still be 20GB free since the size of BTC_Core_Expmnt is supposed to be 300GB.

[BTC_Core_Expmnt]# du -h
102M    ./blocks/index
275G    ./blocks
56K     ./bitcoin-
60K     ./bitcoin-
64K     ./bitcoin-
73M     ./bitcoin-
8.0K    ./bitcoin-
440K    ./bitcoin-
74M     ./bitcoin-
16K     ./lost+found
3.4G    ./indexes/txindex
3.4G    ./indexes
914M    ./chainstate
280G    .

Is 300GB not enough in 2020 to run a full node? I thought it'd do. But, asking for any helpful tips because I cannot see anything else amiss from debug.log.

  • My full node with a txindex is currently sitting at about 280GB - how much of your disk is usable space? Try df -h - a portion of the physical disk size will be lost to filesystem overhead – Raghav Sood Jan 20 at 12:05
  • @RaghavSood Thank you. Yeah I piled on another 100GB and am running that reindexing again. In a few hours I will know. If it completes I'll note that with another confirming comment so anyone stumbling in will have at least that to go on. – MountainMan Jan 20 at 13:23
  • What OS are you using? There is currently an issue with macOS where some files are larger than they should be and sometimes those files have incorrectly reported sizes. – Andrew Chow Jan 20 at 17:23

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 grinding on... Well then what is all this? ::

Your node was not fully synced, so after it finished reindexing the blocks on disk, it continued to download blocks from its peers and finish syncing.

| improve this answer | |
  • It is a CentOS. It must've been disk space issue, the process is taking a few hours, but it is over 40% this time whereas it always fell over between 11 and 19% before. Cheers. – MountainMan Jan 20 at 21:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.