Turkey (Turkish)
Germany (German)
Worldwide (English)
Record full error
Get the first real error message with time information in the journal, service and kernel log instead of the general warning on the screen.
Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
No space left on device does not only mean the disk capacity is full. The filesystem inodes may be exhausted, a deleted large file may be held open by a process, reserved blocks may be in use or a different mount point may be full.
write error: No space left on device
/dev/mapper/almalinux-root 100%
Inodes: IUse% 100%No space left on device does not only mean the disk capacity is full. The filesystem inodes may be exhausted, a deleted large file may be held open by a process, reserved blocks may be in use or a different mount point may be full.
Get the first real error message with time information in the journal, service and kernel log instead of the general warning on the screen.
Test service, disk, network, permission, security policy and application configuration separately without changing them at the same time.
The service name, package manager and firewall tool may be different on Ubuntu/Debian and AlmaLinux/Rocky/CloudLinux.
Keep a second session, console, snapshot or current backup for SSH, network, firewall, boot and disk changes.
Do not blindly delete a database, mail queue or active log file with rm.
Meaning: The filesystem cannot write new data.
Possible cause: Capacity, inode or quota is exhausted.
Meaning: The root filesystem is completely full.
Possible cause: Log, backup, cache, container or database files.
Meaning: No inode remains to create a new file.
Possible cause: A large number of small cache, session or mail files.
Meaning: Area is in an invisible open file or different mount layer.
Possible cause: Deleted open file ya da bind mount.
Meaning: The systemd journal grew.
Possible cause: There is no retention limit or an error loop exists.
Meaning: The container image, layer or JSON logs grew.
Possible cause: Retention and image cleanup are missing.
Meaning: Boot cannot find space for new kernel.
Possible cause: A large number of old kernels.
Meaning: The free space may be exhausted for a normal user.
Possible cause: ext filesystem reserved area.
No error records were found matching this expression.
df -hT
df -i
findmnt -o TARGET,SOURCE,FSTYPE,OPTIONSShows capacity, inode and mount structure.
du -xhd1 / 2>/dev/null | sort -h
du -xhd1 /var 2>/dev/null | sort -hShows large directories within the same file system
find /var -xdev -type f -size +500M -printf '%s %p\n' 2>/dev/null | sort -n | tail -n 50Lists files over 500 MB.
lsof +L1Shows files that were deleted but are held open by a process.
journalctl --disk-usage
journalctl -p err -n 100 --no-pagerShows the journal size and the error loop.
find /var -xdev -type f -printf '%h\n' 2>/dev/null | sort | uniq -c | sort -n | tail -n 40Identifies the inode-consuming directories.
APT cache, snap revisions, systemd journal, and /boot kernel packages should be measured.
apt-get clean --dry-run 2>/dev/null || truesnap list --all 2>/dev/null || truedpkg -l 'linux-image*' | grep '^ii'DNF cache, journal, kernel packages, user quota and CloudLinux LVE logs must be checked.
dnf clean packages --assumeno 2>/dev/null || truerpm -q kernelrepquota -a 2>/dev/null || trueBackup directories, domain logs, mail queue and panel temp files must be analyzed separately from normal system directories.
du -sh /backup /var/lib/psa/dumps /usr/local/psa/PMM/tmp 2>/dev/nulldu -sh /home/*/logs /var/www/vhosts/system/*/logs 2>/dev/null | sort -h | tailexim -bpc 2>/dev/null || postqueue -p 2>/dev/null | tailRecord the exact on-screen or logged error message with its timestamp, then test the service, network, disk, and security layers separately.
The package manager, firewall, network manager, and some service names differ by distribution family. The distribution section on the page explains these differences.
A restart may restore service temporarily, but restarting before collecting logs and resource data can hide the root cause.
Read-only diagnostic commands are generally safe. Configuration, firewall, disk, and recovery changes require console access, a backup, and a rollback plan.
The Linux layer is the same, but control-panel service wrappers, firewall plugins, and vendor packages must also be considered.
Keep a second session and the provider console open during SSH, firewall, network, or boot changes.
No. Technical accuracy and coverage provide a strong foundation, but rankings also depend on competition, site authority, internal links, speed, and user behavior.
We analyze Ubuntu, Debian, AlmaLinux, Rocky and CloudLinux service, disk, network, security, performance and boot problems with log data.