pull down to refresh
in order to do this, I'd need somewhere to put all the blocks during IBD and then prune the SSD?
I still don't have any drives >1TB
but that's helpful to know.
Raw block storage is on the HDD, they are sequential and don't need the benefit of the SSDs random I/O writing speed. The chainstate/ utxo set are on the SSD and this is where the speed is needed for validation.
No pruning needed. You can store on HDD and SSD < 1TB will handle everything else. Can even fit electrum server on the SSD as well in this scenario.
Even a 1TB SSD and a 1 TB HDD will allow you to work with what you have for longer and then by the time we need to get new hardware the hardware situation should look different.
I use proxmox and an ubuntu VM to achieve this. Claude helped a lot in working through the pain points.
interesting. thanks for the pointers.. I'm not ready to take this project on, but at 85% disk fullness, I'm close to needing to accomplish this.
You mean with:
blocksdir=/path/to/hddPut the blocks onto a slow hard drive and keep only the chainstate and the other small stuff on the fast SSD.
Yes exactly
It's possible to separate a full archival node between your existing SSD (not 2tb) and a HDD (probably have one lying around). No real performance loss that I've noticed once ibd is complete which you already have.
Depends on your setup how easy this would be.