run out of disk space

[alpro]

Hello,

I am quite new to Cloudron.

I have installed a couple of apps on quite decent hardware (Ryzen 3 low power, 16 GB RAM, 256 GB SSD as the main disc, 4 TB and 6 TB as the data drives). So far everything went silk-smooth.

Then I was copying some photos to Next Cloud installation. Left it to copy 2 large folders over the night time . By the morning the system is not responsive any more. Seems like it ran out of disk space.

How can I free some of it to get my Cloudron back? When I try to connect to MY.DOMAIN.COM it displays CLOUDRON IS OFFLINE. TRYING TO RECONNECT.

Any suggestions highly appreciated.

[nebulon]

Hi and welcome here. In this case probably delete some data uploaded into Nextcloud, given that you probably have the data on local disk where you uploaded from. Then go over our docs at https://docs.cloudron.io/troubleshooting/#recovery-after-disk-full

[alpro]

Thank you very much for your prompt reply.

In the system there are 3 disks: 256 GB system drive, 4 TB and 6 TB data drives. Next Cloud has 4 TB for its exclusive use and there should still plenty of free space on this drive.

The point is that this is 256 GB system drive that seem to ran out of free space.

My question is what and from where should be deleted from the system drive.

[threetrees3]

How did you allocate the 4TB to Nextcloud?

[alpro]

4 TB has been mounted to the hardware system from the very beginning. Then I have mounted this 4 TB drive for Cloudron use. Then after installing Nextcloud I have added this mount point for the app and moved all Nextcloud data to this volume through app control panel (STORAGE - MOVE DATA).

[nottheend]

Anyone else observing that cloudron grows over time? After maybe 6 to 8 month it looks like below.
I have 8 apps installed, all the app data sums up to not more than 50 MB. Only exception is the platformdata with 1 GB.

Is there anything I can do to reduce it?
I have another free volume availble, but I am not sure what I can use it for to release /root, which is /dev/sda1 mounted at /

• docker 16 GB
• /apps.swap 4 GB
• docker-volumes 4 GB
• Everything else (Ubuntu, etc) 8 GB

[RazielKanos]

for me it's:
docker 23.7 GB
docker-volumes 12.58 GB
/apps.swap 4.29 GB
platformdata 1.48 GB
nextcloud 1.26 GB
immich 463.9 MB
Wordpress 365.28 MB
Mastodon 275.26 MB
Pixelfed 86.99 MB
boxdata 14.79 MB
maildata 2.9 MB
bitwarden 368.64 kB
pdf 90.11 kB
officeserver 32.77 kB
Typebot 12.29 kB
Chatwoot 12.29 kB
Kutt 8.19 kB
Pairdrop 4.1 kB
Everything else (Ubuntu, etc) 11.66 GB

No clue why the first are so large

[nottheend]

Thanks. Then my server is probably not an exception. Just trying to plan the storage needed for the cloudron backend a bit ahead, which I find difficult as of now

[nottheend]

After moving to a new server, the exact same config restored from the backup has only 30GB disk usage, compared to 38GB before

Edited this post after waiting for recreation of the storage utilization

[jagadeesh-s2104]

@nottheend @RazielKanos -

I have the same problem as well.

I will create a backup, stop the VM, then use the backup settings file to create a new VM and restore the backup settings file in the new instance of Cloudron.

I've been using Cloudron for about 3 years, and I have done this around 4 or 5 times.

The Docker images, overlay, etc., are the headache.
For me, it will balloon to 70+ GB, and if I restore, it will be around 40 GB.

[timconsidine]

Does docker image prune help here, to avoid reinstalling ?-

[RazielKanos]

any feedback from the devs? @nebulon @girish

[jagadeesh-s2104]

@timconsidine Yes, thank you!

I do that with other VMs. But I remember reading somewhere that we should not do anything with the Cloudron VM.

[timconsidine]

@jagadeesh-s2104 said in run out of disk space:

@timconsidine Yes, thank you!

I do that with other VMs. But I remember reading somewhere that we should not do anything with the Cloudron VM.

Yes, generally you don’t need to and shouldn’t do something on the server command line, but I think this is an exception. @staff will jump in here to clarify.

[girish]

For the space taken up by docker volumes, this is a bug and fix is already in the upcoming release. You can run docker volume prune --all --force to free up that space. You can do an additional docker system prune -a to clear up stale images etc.

Otherwise, the space usage looks normal to me. Nothing stands out.

[alpro]

@girish Can I run the command today? Or it has not been implemented yet? Is it correct if I SSH to the server and run the command as the admin from there?

[necrevistonnezr]

Yes, that’s a build-in docker command that you can run in your ssh terminal