Is this normal?
Is it normal for Cloudron to take 81GB of storage space?
A Former User last edited by
@cyberfreakde I’d say the larger issue here is why there’s no breakdown of the storage below for you
@atrilahiji I don't quite get what you mean I was hiding all my app names if thats what you wanted to know.
@cyberfreakde That's not normal. Could it be that you moved your backups to an external storage after some time? In that case, maybe you have to remove the old backups from
/var/backupsmanually. You can also use
du -hcs /*to figure where all the space is getting used.
@girish Not old backups because I never backed up locally. However I saw
/var/lib/docker/overlay2has a size of 83GB.
@cyberfreakde df does not report the docker directory size properly. you can use
docker system dfto get the docker size. You can also run and try to remove old images with
docker image prune -a. The prune should have been automatic but maybe something caused it to fail.
subven last edited by
What are your values for
- Docker images
- Platform data
- Backup data
from Cloudrons system info?
How much RAM ans SWAP does your server has?
Size of /var/logs and /var/backups? Please also take a look at the output from du -hcs /* as @girish suggested.
What confuses me is that your docker system df shows over 50GB of data but your Cloudron overview does not have a bar that represents that amount of space (should be the red or orange bar in your example). Instead the green bar seems off.
This is an example from one of my instances. The Server has 16GB RAM and 4GB SWAP.
PS: Your headline should be a bit more descriptive than clickbaiting.
@subven I have 32GB RAM.
@cyberfreakde Essentially "everything else" is
Total disk size-
all the locations cloudron knows about. Just to double confirm, are you saying that
/var/lib/docker/overlay2is the only place on your filesystem which seems to consume this large amount of space? You might have to do du -hcs on various directories to see where the disk space is being used.
To help with the calculations, first see the
df -houtput. This is the disk usage at the block level. Can you also confirm that it says ~96GB used there?