# What to do when Rust logs fill the drive

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Server management](https://rustsc.com/learn/management/index.html.md)

Identify which logs are growing before deleting anything. The combined size matters, but the fastest-growing file tells you what is likely to fill the drive again.

## Measure the game and host logs separately

Compare the size of the game’s log folder and any framework log folder, then repeat after a busy period. On Linux, if the game logs to systemd, `journalctl --disk-usage` reports how much the journal uses. Journal retention settings apply to the journal itself. A separate framework log file needs its own retention setting.

## Keep an example of the repeating problem

If one error repeats, save a short excerpt with its times before moving closed logs to a separate drive. Leave the active world and current log in place. Adjust retention in the software that owns the files. Confirm the next busy session produces readable new logs and that the drive is no longer losing space at the old rate.

## Sources

- [GNU du manual](https://man7.org/linux/man-pages/man1/du.1.html)
- [systemd journal storage settings](https://freedesktop.org/software/systemd/man/latest/journald%40.conf.html)
- [systemd journalctl reference](https://www.freedesktop.org/software/systemd/man/latest/journalctl.html)

## Related resources

- [Free disk space](https://rustsc.com/support/guides/free-disk-space/index.html.md)

---

HTML version: https://rustsc.com/learn/management/rust-disk-filling-with-logs/
