<ol>
<li>Disk space issue:</li>
</ol>
<p>Each system only has 73GB maximum on / (which is where you are running from).
The live Cardano chain is now 50GB on it's own. I'm not sure of the testdb size.</p>
<p>Make the / volume larger on each system eg 120GB maybe.</p>
<ol start="2">
<li>Differences between BP and Relay system:</li>
</ol>
<p>The BP system has used 70GB of / while the Relay has used 65GB of /</p>
<p>So, what has used the extra 5GB somewhere on the BP system?
Left over logs or code?</p>
<p>cd to /home and do a 'du -h .' there to see if you can spot if the space has been used by a different user.</p>
<p>If not obvious there then you will need to review other directories off of / to narrow down where the extra 5GB has been used.
Often /var/log can use a lot of disk space logging things.
Also check /tmp</p>

CC BY-SA 4.0
2022-04-21T06:25:17.133Z
That's the thing though, I provisioned 150 GB for each of the environments.
Matthias Sieber
CC BY-SA 4.0
2022-04-21T06:33:28.817Z
Yes, the *whole* environment may be 150G, but as @MC_Brisbane points out, the partition where the `node` is storing its data is smaller.
Erik de Castro Lopo
CC BY-SA 4.0
2022-04-21T06:22:11.373Z
2022-04-21T06:22:11.373Z
MC_Brisbane - JUST Pool
<p>You need to find out which files are filling up the disk.</p>
<p>A command like:</p>
<pre><code>find / -type f -printf &quot;%15s    %p\n&quot; | sort -nr | head -30;
</code></pre>
<p>might help.</p>

CC BY-SA 4.0
2022-04-21T06:22:01.540Z
2022-04-21T06:22:01.540Z
Erik de Castro Lopo
<p>I had two cardano-node instances running via kvm on one physical machine.
Both nodes were running on mainnet for a while before I switched them over to testnet (to prepare for turning these into a stake pool).</p>
<p>I gave both environments (labelled <strong>BlockProducer</strong> and <strong>Relay</strong>) the same resources, incl. 150 GB of disk space.
<a href="https://i.sstatic.net/CQgNV.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/CQgNV.png" alt="hard disk space for virtual environments" /></a></p>
<p>When logging into both environments, I noticed that BlockProducer's cardano-node process crashed with a <code>FileSystemError</code>, stating that there is no space left on the device.
Restarting the process (also after rebooting BlockProducer) did not change this.</p>
<p><a href="https://i.sstatic.net/HYH5A.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/HYH5A.png" alt="FsDeviceFull" /></a></p>
<p>These are the outputs for <code>df -h</code> and <code>du -h -d 1</code> in the respective cardano-node directories. Left is the (working) Relay, while the right side shows the BlockProducer environment.<a href="https://i.sstatic.net/Q0mBO.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Q0mBO.png" alt="Relay and BlockProducer comparison" /></a></p>
<p>The host system running the kvm daemon still has 210 GB of available disk space.
Did I simply under-provision the virtual disks or what is going on here?</p>
<p>Why is Relay still running though? I installed the same software and configured both environments the same.</p>

<cardano-node><stake-pool><ubuntu><linux>
One node surprisingly running out of disk space
# One node surprisingly running out of disk space

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

I had two cardano-node instances running via kvm on one physical machine.
Both nodes were running on mainnet for a while before I switched them over to testnet (to prepare for turning these into a stake pool).

I gave both environments (labelled **BlockProducer** and **Relay**) the same resources, incl. 150 GB of disk space.
[![hard disk space for virtual environments](https://i.sstatic.net/CQgNV.png)](https://i.sstatic.net/CQgNV.png)

When logging into both environments, I noticed that BlockProducer's cardano-node process crashed with a `FileSystemError`, stating that there is no space left on the device.
Restarting the process (also after rebooting BlockProducer) did not change this.

[![FsDeviceFull](https://i.sstatic.net/HYH5A.png)](https://i.sstatic.net/HYH5A.png)

These are the outputs for `df -h` and `du -h -d 1` in the respective cardano-node directories. Left is the (working) Relay, while the right side shows the BlockProducer environment.[![Relay and BlockProducer comparison](https://i.sstatic.net/Q0mBO.png)](https://i.sstatic.net/Q0mBO.png)

The host system running the kvm daemon still has 210 GB of available disk space.
Did I simply under-provision the virtual disks or what is going on here?

Why is Relay still running though? I installed the same software and configured both environments the same.

**Tags:** cardano-node, stake-pool, ubuntu, linux

---

## 2 answers

### Answer by username_1 on 2022-04-21. Score: 1 | Accepted answer

1. Disk space issue:

Each system only has 73GB maximum on / (which is where you are running from).
The live Cardano chain is now 50GB on it's own. I'm not sure of the testdb size.

Make the / volume larger on each system eg 120GB maybe.

2. Differences between BP and Relay system:

The BP system has used 70GB of / while the Relay has used 65GB of /

So, what has used the extra 5GB somewhere on the BP system?
Left over logs or code?

cd to /home and do a 'du -h .' there to see if you can spot if the space has been used by a different user.

If not obvious there then you will need to review other directories off of / to narrow down where the extra 5GB has been used.
Often /var/log can use a lot of disk space logging things.
Also check /tmp

> **Comments:**
> **username_0**: That's the thing though, I provisioned 150 GB for each of the environments.  
> **username_2**: Yes, the *whole* environment may be 150G, but as @MC_Brisbane points out, the partition where the `node` is storing its data is smaller.  

---

### Answer by username_2 on 2022-04-21. Score: 1

You need to find out which files are filling up the disk.
A command like:
find / -type f -printf "%15s    %p\n" | sort -nr | head -30;

might help.


---

