Direct answer
Use monitoring on the filesystem that holds your world and persistent plugin data. Disk bytes and available inode counts can be exhausted independently.
Recommended procedure
- Run
df -h /srv/minecraftanddf -i /srv/minecraft, substituting the true server directory. - Check world, logs and backup sizes with
du -shon existing directories and confirm which disks they use. - Collect baseline readings at idle, after large world-generation sessions and before scheduled backups.
What to change
df -h /srv/minecraft
df -i /srv/minecraft
du -sh /srv/minecraft/world* /srv/minecraft/logs 2>/dev/null- Choose an alert threshold with adequate time to respond rather than waiting until 100% full.
- Rotate expendable logs and manage old backups only after validating an offsite backup and retention policy.
- If data grows unexpectedly, inspect plugin databases and chunk generation separately before changing world files.
How to verify the result
Ensure alerts trigger on the relevant filesystem and that scheduled backups still complete with sufficient free disk and inodes.
Version and safety notes
Hosted panels can use disk quotas beyond filesystem reports. Avoid automatic cleanup scripts that delete active worlds, region files or plugin databases.
Official references
Related guides
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.