Cloudron Forum

@jdaviescoates said in Volume disk space strangeness:

/me goes to reduce the size of the volume back to a perfectly sufficient 10 GB...

Oh, bollocks. You can't decrease the size of Hetzner Cloud Volumes, only increase them. So I'd have to create a whole new one and then and then and then...can't be bothered with all that so I guess I'll just stomach the slightly increased cost of 15 GB over 10 GB.

Debugged this with @ZeZaung a bit. Somehow, it was possible to re-run cloudron-setup on the existing install and this reset the database even though the app containers and data were still there. I have made a fix which should hopefully mitigate the problem.

@girish Seems to be all clear. No got any notification in system area. So alert was it misunderstood?

Many thank's!

@jdaviescoates said in Nextcloud says 5.3GB used, Cloudron says Nextcloud is 19.16GB, why?:

That's "just" a difference of 2.66GB (which I guess could mostly be just Nextcloud files themselves)

So, assuming that is mostly just Nextcloud files themselves (I may do a clean install at some point just to see how big that is), I think this can be marked as solved.

Ah we did hit that kernel/initramfs issue with /boot getting filled up by Ubuntu already before. If it is 100% full even the autoremove fails.

Would be good to actually not just maybe warn about that, but see how the whole situation can be mitigated in the first place. Afterall it is not much use to have that many kernel versions around.

@girish & @marcusquinn thanks for the hints!

Finally the AWS guide did the trick, it was a 2 step approach (in my case):

sudo growpart /dev/sda 3

sudo resize2fs /dev/sda3