Bitcoin core - 350GB now is 35GB ?

[lndlnd]

I moved to the new version - Moved over all 350GB and started up 0.21.0  .  Great....   
After a while I checked the size and its now just the newer blocks and 35GB -   Size is nice but if I move it again to another PC will have have to download all the 350 Again.  ?   What setting should I use to start again with the 350 and not get it chopped ?    Thanks

[1715408270]

1715408270

[achow101]

In recent releases, Bitcoin Core will automatically enable pruning the first time you start the GUI and it detects that there is not a lot of disk space. When you go through the first start wizard, be sure to pay attention to all of the checkboxes and uncheck the any that enable pruning. This setting is (unfortunately) stored separately from the datadir so when you copy datadirs to another machine, it is lost. If you create a bitcoin.conf file and add the line prune=0, this should forcibly disable pruning always so this doesn't happen. In that case, that setting will carry over as it is set in the bitcoin.conf file.

[lndlnd]

Thanks so to fix this for myself . I should again copy all the data over.   Then edit the bitcoin.conf file first . Make sure prune=0 first.  Then start again and download the last two days transactions.
How can we highlight this to other guys upgrading?

In recent releases, Bitcoin Core will automatically enable pruning the first time you start the GUI and it detects that there is not a lot of disk space. When you go through the first start wizard, be sure to pay attention to all of the checkboxes and uncheck the any that enable pruning. This setting is (unfortunately) stored separately from the datadir so when you copy datadirs to another machine, it is lost. If you create a bitcoin.conf file and add the line prune=0, this should forcibly disable pruning always so this doesn't happen. In that case, that setting will carry over as it is set in the bitcoin.conf file.

[HCP]

It's not really an issue if you're simply updating the application itself without moving the blocks, migrating to a new PC and/or you still have a decent amount of storage space available.

I just did this just now (upgraded to 0.21.0) and had no issues with it whatsoever... it didn't "auto prune" my blocks or change any of the settings.

I have noticed however, that if I run the -choosedatadir option and set it to use the current location of my bitcoin datadir, because the current diskspace free is less than the current blockchain size (ie. 350+gigs), it auto-enables the pruning option:


Even though it doesn't need to actually download anything, because the blocks are already there...

So, I assume for anyone that copies the datadir first and then runs Bitcoin Core... it will do the same thing, unless there is >350gigs free space etc.


If I untick pruning, it then "warns" about the disk free space in red: