Turkey (Turkish)
Germany (German)
Worldwide (English)
Kapasitedisk usage is measured with df -h
Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
When the disk or inode usage reaches 100% on Plesk server, the panel, websites, mail, MariaDB, and backups may fail simultaneously. The correct solution is not to randomly delete files, but to identify the cause of the mount, the type of data consuming space, and the reason for growth.
No space left on device
Disk quota exceeded
Failed to write session data
MariaDB: Unable to create temporary file
Plesk backup failed: insufficient disk spaceDisk capacity limits the total byte size of files, while inode limits the number of files and directories. Even if there is free space in GB, millions of small files can consume 100% of inode usage, preventing new files from being created.
First, determine which mount is full using df -hT. /, /var, /var/lib/psa/dumps or separate /var/www partition carry different reasons.
Plesk backups can consume significant disk space by default under /var/lib/psa/dumps. However, active or single redundant backups should not be deleted.
Domain logs under /var/www/vhosts/system/alanadi/logs, mail data grows according to distribution under /var/qmail or /var/mail structure.
Deleted files but open large files held by running process do not appear in the output and continue to use the df area. lsof +L1 provides this distinction.
When the disk is completely full, first create a small safe space and stabilize the logs and services. Then, perform a thorough cleanup and increase capacity; using rm -rf without researching large directories can cause serious data loss.
Search for the phrase you see in the email, browser, or SSH log. Each card includes meaning, probable cause, and safe initial action.
Meaning: File system cannot write new data or metadata.
Possible cause: Disk byte capacity or inode has expired.
Meaning: Account or subscription has exceeded the defined quota.
Possible cause: Plesk subscription kota limiti or filesystem quota.
Meaning: File system cannot find inode for new file.
Possible cause: Session, cache, maildir or small file explosion.
Meaning: The PHP session file cannot be written.
Possible cause: /var/lib/php/session or /tmp area inode permission issue.
Meaning: Failed to create a new file on the database tmp or datadir.
Possible cause: Disk/inode full or tmpdir issue.
Meaning: Estimated space required for backup could not be found.
Possible cause: Old backups, large dump, or incorrect retention.
Meaning: Rotation is not working or the application is frequently writing the same error.
Possible cause: logrotate is broken, debug mode is open or under attack traffic.
Meaning: The mount may have been made read-only after the kernel file system error.
Possible cause: Filesystem or disk hardware error.
No records matching this expression were found.
Commands are for root access. Collect only status and logs first; Do not change the permanent setting without seeing the reason.
df -hT
df -iDisplays the byte and inode usage of all mounts.
du -xhd1 / 2>/dev/null | sort -h
du -xhd1 /var 2>/dev/null | sort -hShows the top-level directories consuming space within the same filesystem.
du -xsh /var/lib/psa/dumps/* 2>/dev/null | sort -h | tail -n 30List largest Plesk backup folder and files.
find /var/www/vhosts/system -path '*/logs/*' -type f -size +100M -printf '%s %p
' 2>/dev/null | sort -n | tail -n 30Displays domain logs over 100 MB by size.
lsof +L1 | sort -k7 -n | tail -n 30Shows files that are kept open by the process and using space, even though they are deleted.
for d in /var/www/vhosts /var/lib/php /tmp /var/qmail; do [ -d "$d" ] && echo "$d $(find "$d" -xdev -type f 2>/dev/null | wc -l)"; doneCompares the number of files in the root directories where inode usage is likely to be high.
iostat -xz 1 3
journalctl -k -n 120 --no-pagerShows reasons for disk density, I/O error, and read-only filesystem.
After the dolan mount and data type are determined, a secure short field is opened, the growth reason is stopped, and a permanent capacity plan is applied.
Cleaning /home while /var is full does not provide any benefit. Analyze on the same mount.
df -hT && df -iClassify backup as domain log, mail, database, cache, and deleted open file.
Allocate limited space from low-risk targets such as package cache or verified old temporary files; do not touch DB/mail data.
If the error log explosion, spam mail, failed backup loop, or cache production continues, stop the source first.
Adjust Backup Manager and domain log rotation settings to suit the workload.
Plan partition growth, separate backup storage, and set alarms at 75/85 thresholds.
Backup Manager retention, local/remote copy strategy and incremental chains are checked.
First, resolve the repeating error or attack source; then reduce with logrotate under control.
Spam queue, mailbox usage, retention, and breached accounts are analyzed.
Binary log, slow log, tmp, and actual database growth are separated; table files are not deleted manually.
Find open handle with lsof +L1; release the area by reloading/restarting the related service.
The inode can be 100% or the partition to be written is full.
On Linux, the default local backup location is usually /var/lib/psa/dumps.
Deleting the active file may not immediately free up space and can cause data loss. Rotation/truncation should be done carefully.
Displays files that were deleted but are still using disk space because they are being held open by a running process.
First, locate the millions of small files produced by session, cache, mail, or application source; files are deleted according to the retention policy.
Log rotation and backup retention help; regular monitoring is necessary for incorrect configuration or application growth.
Provides space for a short term; if the uncontrolled log, backup, or spam growth continues, the new space will also be filled.
By analyzing cPanel, WHM, CloudLinux, LiteSpeed, MariaDB, Exim and security layers together, we fix the root cause of the failure instead of just removing the service.