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

  1. Run df -h /srv/minecraft and df -i /srv/minecraft, substituting the true server directory.
  2. Check world, logs and backup sizes with du -sh on existing directories and confirm which disks they use.
  3. 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
  1. Choose an alert threshold with adequate time to respond rather than waiting until 100% full.
  2. Rotate expendable logs and manage old backups only after validating an offsite backup and retention policy.
  3. 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

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000