Migrate blocksdir to HDD?
See original GitHub issueBitcoin Core now supports migrating the gigantic blocks
directory out of the data directory. A lot of people have both HDD and SSD, then they could complement one another perfectly.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
Migrate chainstate to SSD, or load it to memory #14904 - GitHub
A viable solution is migrating chainstate to SSD, while keeping blocks stored on HDD. You can start Bitcoin Core with -blocksdir to specify ......
Read more >If you don't have enough space for the blockchain in your SSD ...
With Core closed, move the Chainstate folder from the slow drive to the fast drive ... Point datadir at the SSD and blocksdir...
Read more >Moving the Bitcoin Core Data Directory - Bitzuma
An ever-growing data set causes smaller hard drives to fill up quickly ... These problems can be solved by moving and copying Bitcoin...
Read more >bitcoin core - Change IBD Location Prior to Download
... and move the block storage only to the external drive by adding blocksdir=/path/to/external/blocksdir to your bitcoin.conf.
Read more >Change Bitcoin Core Data Directory - BitcoinWiki
An ever-growing data set causes smaller hard drives to fill up quickly. Furthermore, a new wallet can't be used until the full block...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@PierreRochard Pros of HDD: Large volume, cheap Cons of HDD: Very poor random access performance Pros of SSD: Turbo random access performance & sequential performance Cons of SSD: Small volume, relatively expensive
The UTXO database (chainstate) is heavily accessed, which is quite a nightmare for HDDs. Storing gigantic block data on a SSD is quite a waste, because it’s not frequently accessed.
Therefore, it’s optimal to use HDD for block storage only, while SSD is supposed to deal with heavily accessed chainstate/txindex etc.
“Migrating block storage” could be worded in other ways, like “migrating chainstate to your turbo SSD to significantly accelerate syncing process”.