mirror of
https://github.com/bitcoin/bitcoin.git
synced 2025-02-04 10:07:27 -05:00
7fa851fba8
While a node is still catching up to the tip that it is aware of via the headers, the user can currently use to fetch blocks close to the tip. These blocks are stored in the current block/rev file which otherwise contains blocks the node is receiving as part of the syncing process. This creates a problem for pruned nodes: The files containing a fetched block are not pruned during syncing because they contain a block close to the tip. This means the entire file will not be pruned until the tip have moved on far enough from the fetched block. In extreme cases with heavy pruning (550) and multiple blocks being fetched this could mean that the disc usage far exceeds what the user expects, potentially running out of space. |
||
---|---|---|
.. | ||
blockchain.cpp | ||
blockchain.h | ||
client.cpp | ||
client.h | ||
external_signer.cpp | ||
fees.cpp | ||
mempool.cpp | ||
mempool.h | ||
mining.cpp | ||
mining.h | ||
net.cpp | ||
node.cpp | ||
output_script.cpp | ||
protocol.h | ||
rawtransaction.cpp | ||
rawtransaction_util.cpp | ||
rawtransaction_util.h | ||
register.h | ||
request.cpp | ||
request.h | ||
server.cpp | ||
server.h | ||
server_util.cpp | ||
server_util.h | ||
signmessage.cpp | ||
txoutproof.cpp | ||
util.cpp | ||
util.h |