Identify the affected filesystem
A full filesystem can stop mail, databases, backups and web requests. Check which mount is full and whether the issue is bytes or inodes. A large total on one mount does not prove that another mount has capacity. Capture current alerts and confirm backups before deleting anything.
Inspect usage by approved directories and account for recent backup archives, mail queues, application uploads and logs. A file deleted from the directory can still occupy space while a process holds it open; identify the owning process before choosing a safe release procedure.
Separate symptoms from the cause
If logs are growing quickly, examine the repeated error and its source. Blindly truncating logs can remove incident evidence and may only buy a short reprieve. Review rotation and retention, then correct the underlying application or mail failure.
For backup storage, verify the retention policy and the existence of a usable off-server copy before removing old archives. Do not delete database files or mailboxes to free space without a service-specific recovery plan.
Restore headroom and verify
Choose a reversible or approved cleanup, or expand storage after checking filesystem and provider requirements. Confirm database and mail services recover, retry the original failing operation and verify a fresh backup can complete. Monitor both capacity and growth rate, and set thresholds that leave enough time for the team to respond.
Document the directories examined, data removed, current free space and the owner of the long-term fix.
Further reading
Read the official documentation. For help applying these checks, explore Clouvenix services.