<p>The bitcoin.conf option must be <code>prune=1000</code>, not <code>pruned=1000</code>. If you specified the latter, it was probably ignored.
You could reduce the number up to 550 (MiB), bitcoind won't start if you choose a lower number.</p>

CC BY-SA 4.0
2022-07-04T22:44:11.617Z
2022-07-04T22:44:11.617Z
Lightlike
<p>I have a testnet VM node running. As I have only limited resources, I did set <code>pruned=1000</code> in the bitcoin.conf file, so the blockchain is pruned down to 1GB. But when I run bitcoind and it downloads the blockchain, I get the error, that no more space is available after downloading 80% or so.
So my question: How do I make sure that the pruned mode is actually enforced?</p>
<p>Thanks!</p>

<bitcoind><testnet><pruning><bitcoin.conf>
How to configure a testnet node to be pruned?
zerotobtc
# How to configure a testnet node to be pruned?

(Asked by: username_0 on 2022-07-04)

I have a testnet VM node running. As I have only limited resources, I did set `pruned=1000` in the bitcoin.conf file, so the blockchain is pruned down to 1GB. But when I run bitcoind and it downloads the blockchain, I get the error, that no more space is available after downloading 80% or so.
So my question: How do I make sure that the pruned mode is actually enforced?

Thanks!

**Tags:** bitcoind, testnet, pruning, bitcoin.conf


---

## 1 answers

### Answer by username_1 on 2022-07-04. Score: 6 | Accepted answer

The bitcoin.conf option must be `prune=1000`, not `pruned=1000`. If you specified the latter, it was probably ignored.
You could reduce the number up to 550 (MiB), bitcoind won't start if you choose a lower number.


---

