The first useful check
A full filesystem can stop an application, but deleting an unfamiliar path can turn a capacity incident into a data-loss incident.
Inputs and prerequisites
Check filesystem space and inode usage, then inspect the largest known application, upload, log and release paths. Keep database files and unknown system paths out of a quick cleanup.
A small, reversible procedure
Identify the owner and retention purpose of a large path, make a bounded change such as log rotation or a documented archive, then recheck space and application behavior.
What to record after the check
Record the filesystem, path, owner, size before and after, and the application check used after the cleanup.
Scope and service boundary
This does not prescribe deletion commands or prove which data is safe to remove. Malaysia, Romania and Switzerland are server-country choices; they do not establish a backup country, facility detail, stock or measured network result.
Documentation used
Primary references for this page. Check the documentation for the version installed in your own environment.