When a Linux server reports a full disk, the article explains three possible causes—actual space exhaustion, inode depletion, or deleted files still held by processes—and walks through eight essential commands, from df and du to lsof, ncdu, iostat, and journalctl, to diagnose and safely resolve the issue.
This article explains why disk‑full issues cripple Linux servers, outlines the concepts of filesystem, LVM and inode space, and provides a step‑by‑step, layered method using df, du, find, lsof and logrotate to locate and safely free space, handle deleted‑but‑open files, clean logs, manage databases, temporary caches, Docker resources, and LVM volumes, and finally set up monitoring and preventive measures.
The article explains that occasional recovery of rm ‑rf deletions is possible, but no single command guarantees full restoration; it outlines the Linux kernel behavior, immediate containment steps, how to examine backups, snapshots, open file descriptors, block‑level imaging, filesystem‑specific tools, verification, and post‑recovery best practices for production environments.
The article explains how the Linux "list open files" (lsof) command can be used to identify which processes occupy ports, hold deleted files, or leak file handles, providing concrete examples, performance tips, and troubleshooting case studies for production environments.
When a Linux server reports a full disk, this guide walks you through eight essential commands to diagnose whether the issue is actual space exhaustion, inode depletion, lingering deleted files, or I/O bottlenecks, and provides a systematic cleanup workflow for production environments.
The article explains how the Linux lsof utility can quickly identify port conflicts, lingering deleted files, and file‑handle leaks, offering practical commands, real‑world case studies, advanced options, performance tips, and integration techniques for effective system troubleshooting.
This guide explains why removing large log files on Linux often leaves disk usage unchanged, reveals the hidden “ghost” processes that keep deleted files open, and provides step‑by‑step commands to identify, release, and prevent such space leaks.
Learn how to quickly locate oversized files and directories on a Linux server, verify safety before removal, use proper commands for secure deletion, and implement automation to prevent future disk‑space emergencies.
This guide explains what port occupation means on Linux, demonstrates how to use lsof and netstat to pinpoint the process holding a specific port, and shows how to safely terminate that process to free the port for your applications.
This article provides a comprehensive walkthrough of the Linux I/O stack architecture, explains key performance metrics, demonstrates how to use tools such as iostat, pidstat, strace and lsof, and presents a step‑by‑step case study for locating I/O bottlenecks on a high‑traffic web server.
This guide introduces four essential Linux commands—lsmod, lsof, lspci, and lsscsi—detailing their purpose, syntax, useful options, and practical output examples, helping system administrators quickly diagnose kernel modules, open files, PCI devices, and SCSI devices.
This guide explains how to use the Linux lsof command‑line utility to list information about files opened by processes—including regular files, directories, sockets, and pipes—while covering options for filtering by file, directory, process name, user, PID, network connections, repeat mode, and more.
lsof is a powerful Linux utility that lists open files, sockets, and network connections for processes; this guide explains its core options, output fields, and practical examples such as identifying files opened by specific processes, directories, users, network ports, and even recovering deleted files.
This guide explains how to use common Linux commands such as netstat, ss, lsof, fuser, and nmap to list listening ports, interpret their output fields, and pinpoint which processes are occupying specific ports on a server.
This guide explains how to use Linux commands such as netstat, ss, lsof, fuser, and nmap to list open ports, interpret their output fields, and pinpoint the processes that are occupying particular ports on a server.
This guide explains how to use netstat, ss, lsof, fuser, and nmap commands on Linux to list open ports, interpret their status columns, and determine which processes are occupying specific ports, with installation tips and example outputs.
This guide shows how to use Linux commands such as netstat, ss, lsof, fuser, and nmap to list listening ports, interpret their output fields, and pinpoint the exact process or program occupying any given port.
This guide introduces four essential Linux commands—lsmod, lsof, lspci, and lsscsi—detailing their purpose, syntax, key options, example outputs, and how to interpret each column for effective system monitoring and troubleshooting.
This guide explains how to use Linux commands such as netstat, ss, lsof, fuser, and nmap to inspect port usage, interpret their output fields, and install missing tools, enabling you to pinpoint which processes are occupying specific ports.
Learn how to use essential Linux commands—lsmod, lsof, lspci, and lsscsi—to inspect kernel modules, open files, PCI devices, and SCSI devices, including syntax, useful options, and practical examples that illustrate interpreting their output for effective system administration.
This tutorial demonstrates how to verify a running Nginx process, deliberately delete its access log, and then use the lsof command together with the /proc filesystem to locate the deleted file descriptor and restore the log data on a Linux system.
When a Linux server triggers a disk‑space alert, you can pinpoint the offending directories or files by using df to view overall usage, du (with depth or max‑depth) or find to list large items, and lsof +L1 to detect deleted files still holding space, then optionally adjust reserved space with tune2fs.
This article explains why disk space may not be freed after deleting large log files on a Linux server, describes the underlying file system mechanisms, and provides a step‑by‑step troubleshooting guide using /tmp cleanup and the lsof command to identify and kill lingering processes.
This guide explains how to use the Linux lsof command to list information about open files, processes, directories, sockets, and network connections, covering basic usage, column meanings, filtering options, repeated mode, and practical examples for system administration tasks.
Learn to quickly diagnose the “Address already in use” error on Linux by listing listening ports with netstat, ss, and lsof, interpreting their output, filtering results, and freeing conflicted ports, with example commands and explanations of each option.
This guide explains practical commands like du, find, and lsof to locate large directories or deleted files consuming disk space, and shows how to adjust reserved filesystem space with tune2fs to reclaim lost capacity.
This guide explains how to use the powerful lsof command to list information about files opened by processes, filter results by file type, user, process name, directory, network connections, and even repeatedly monitor changes, providing practical examples and code snippets for Linux administrators.
This comprehensive guide explains how to use the Linux lsof command to list information about open files, directories, sockets, and devices across processes, covering options for filtering by file, process, user, network connections, and advanced features like repeat mode and combined queries.
This guide explains how to use Linux commands like df, du, find, lsof, and tune2fs to locate large directories, uncover deleted files that still occupy space, and adjust reserved root space, enabling you to resolve unexpected disk‑usage alerts efficiently.
This guide shows how to use df, du, find, and lsof commands to locate large directories, files, and deleted-but-open files that consume disk space, and explains how to adjust reserved filesystem space on Linux.
This guide explains how to use the lsof command on Linux to list open files, filter by process, directory, user, or network criteria, combine options, view UNIX domain sockets, count open files, and even recover accidentally deleted files using file descriptors.
This guide introduces three essential Linux I/O commands—iostat for disk activity statistics, iotop for real‑time I/O usage per process, and lsof for listing open files—detailing installation, output interpretation, key parameters, and practical usage examples.
This tutorial explains how to use the Linux LSOF command to list open files, identify processes using specific ports, filter TCP connections, and continuously monitor network activity in real time with customizable intervals.
This guide introduces three essential Linux I/O commands—iostat for overall I/O statistics, iotop for real‑time per‑process I/O usage, and lsof for listing open files—showing how to install, run, interpret their output, and use common options.
This guide introduces three essential Linux I/O tools—iostat for disk activity and CPU stats, iotop for real‑time per‑process I/O usage, and lsof for listing open files—detailing installation, key output fields, common options, and practical usage examples.
This guide explains how to diagnose unexpected disk usage on Linux servers by using df to view overall usage, du and find to pinpoint large directories or files, and lsof to uncover deleted files that still hold space, plus how to adjust reserved space with tune2fs.
This guide explains the Linux lsof command, its syntax and options, the types of files it can list, and provides numerous practical examples for monitoring open files, identifying processes, inspecting network connections, and troubleshooting system issues.
This guide explains the purpose of the lsof command, its syntax, the types of files it can list, common options, and provides dozens of practical examples for inspecting processes, network connections, and file descriptors on Linux systems.
This guide explains how a file deleted on a Linux system can still be recovered when a running process holds an open file descriptor, detailing the use of tail, lsof, the /proc filesystem, and simple copy commands to restore the data.
This guide introduces ten lesser‑known Linux commands—including rsync, screen, lsof, vimdiff, netcat, and more—explaining their key options, practical use‑cases, and example invocations so you can work faster, automate tasks, and troubleshoot systems efficiently.
The article explains the “Too many open files” error in Kubernetes, clarifies that it refers to exceeding system file‑handle limits, shows how to inspect current usage with ulimit and lsof, and provides step‑by‑step commands to temporarily or permanently raise the limits and troubleshoot the application code.
Learn step‑by‑step Linux techniques to locate hidden disk consumers—using df, du, find, lsof, and tune2fs—to resolve mismatched usage reports, delete lingering open files, and adjust reserved space, ensuring your server’s storage stays under control.
This guide explains how to locate large directories or files consuming disk space on Linux servers using commands like df, du, find, and lsof, and shows how to free space occupied by deleted files or adjust reserved root space with tune2fs.
This guide shows Linux administrators how to use df, du, find, lsof, and tune2fs commands to locate large directories, uncover hidden space consumed by deleted files, and adjust filesystem reserved space, with step‑by‑step examples and screenshots.
This guide shows step‑by‑step Linux commands—df, du, find, lsof, and tune2fs—to pinpoint large directories, uncover hidden space used by deleted files, and adjust reserved root space, helping you resolve mysterious disk‑space alerts efficiently.
This guide explains why the “Address already in use” message appears, defines listening ports, and shows step‑by‑step how to use netstat, ss, and lsof commands to list, filter, and pinpoint the processes occupying specific ports on Linux and macOS systems.
When a Linux server raises a disk‑space alarm, this guide shows step‑by‑step how to locate the offending directories or files using df, du, find, lsof and tune2fs, and explains why reported usage may differ from summed directory sizes.
Learn how to diagnose the “Address already in use” error by listing listening ports on Linux and macOS using netstat, ss, and lsof, understand port concepts, interpret command output, filter results, and find which processes occupy specific ports.
This guide explains how to locate large directories and files consuming disk space on Linux servers using commands like df, du, find, lsof, and tune2fs, and offers tips for handling hidden or deleted file usage.
This guide shows how to quickly locate and resolve the “Address already in use” error on Linux and macOS by using netstat, ss, and lsof to list listening ports, interpret their output, and filter results for specific services or ports.
Learn step‑by‑step how to use netstat, ss, and lsof commands to list listening ports, filter results, and pinpoint the exact process occupying a specific port on Linux and macOS systems.
Even when a Linux system reports a full disk, deleted files may still occupy space because active processes keep them open; using commands like df, du, and lsof reveals hidden usage, and understanding the virtual file system, inode structures, and link management explains how to release the space.
The article explains why Linux can report a full disk despite apparent free space, showing how deleted files held open by processes keep their blocks allocated, and walks through using df, du, and lsof to identify the issue, then details the virtual file system architecture, inode handling, and file‑deletion mechanics.
This guide explains why careful file deletion matters, introduces Linux tools like lsof and extundelete for recovering mistakenly removed files, and provides step‑by‑step commands, installation instructions, and precautions to maximize recovery success while avoiding data loss.
This article explains why a Linux system can report a full disk even after files are deleted, covering the role of open file handles, the lsof command, and the virtual file system architecture that manages inodes, dentries, and link counts.
Even when the `df` command shows a full disk, hidden deleted files held open by processes can consume space, and understanding this requires diving into Linux’s virtual file system architecture, including superblocks, inodes, file and dentry objects, as well as link types and file‑process interactions.
This guide explains how to diagnose the “Address already in use” error by listing listening ports with netstat, ss, and lsof, interpreting their output, filtering results, and locating the offending process on Linux and macOS systems.
Learn step-by-step methods to locate large directories and files consuming disk space on Linux servers, using commands like df, du, find, and lsof, plus tips for handling deleted files and adjusting reserved space with tune2fs to reclaim lost storage.
This guide explains why NFS mounts can appear busy, how to identify the blocking processes with lsof and fuser, and step‑by‑step commands to safely kill those processes or perform a lazy unmount, ensuring the filesystem is cleanly detached.
This guide explains why NFS mounts can become "device busy", shows how to locate the processes holding the mount with lsof and fuser, demonstrates safe termination of those processes, and covers both regular and lazy unmount techniques to reliably release the filesystem.
This guide explains why careless file deletion can cause serious loss, introduces Linux tools like lsof and extundelete for recovering deleted files, and provides step‑by‑step commands for installing, locating open file descriptors, and restoring individual or all deleted data safely.
This guide explains how to use the versatile lsof utility on Unix-like systems to list open files, discover which processes are using specific network ports, filter by user or command, and combine options for advanced troubleshooting and security monitoring.
Learn step-by-step Linux techniques—including df, du, find, and lsof commands—to pinpoint large directories or files, filter results, handle hidden space consumption, and adjust reserved filesystem space, ensuring you can efficiently resolve unexpected disk usage issues on your servers.
This guide explains how to diagnose unexpected disk usage on Linux by using df, du, find, and lsof commands, demonstrates efficient ways to locate large directories or deleted files, and shows how to adjust reserved space with tune2fs to reclaim lost storage.
This guide explains how to use Linux commands such as df, du, find, and lsof to quickly locate directories, files, or deleted resources that are consuming disk space, and shows how to adjust reserved space with tune2fs to recover seemingly missing storage.
This guide explains why careful file deletion matters, introduces Linux tools like lsof and extundelete for recovering accidentally removed files, and provides step‑by‑step commands, installation instructions, and precautions to successfully restore data from ext3/ext4 partitions.
This guide explains why careless file deletion can be disastrous, then walks through two Linux recovery techniques—using lsof to capture still‑open deleted files and employing extundelete to restore data from ext3/ext4 partitions—complete with commands, parameters, and practical tips.
The article explains why Linux can show a full disk despite apparent free space, detailing how deleted files remain occupied by open processes, the role of the virtual file system (VFS), inode structures, and how commands like lsof reveal these hidden usages.
The article explains why a Linux system may report a full disk even after deleting files, detailing how open file handles keep space occupied, and walks through the virtual file system architecture—including superblocks, inodes, file and dentry objects—while demonstrating diagnostic commands like df, du, lsof, and illustrating link types and file‑process interactions.
When a large file is deleted on a Linux server but the '/' partition still reports 100% usage, a running process likely still holds the file open, preventing space reclamation; this article explains the cause, shows how to find deleted‑but‑in‑use files with lsof, and offers recovery steps such as killing processes, restarting services, truncating logs, and adjusting reserved block percentages.
This guide explains how to restore accidentally deleted files on Linux by handling two scenarios—when the deleting process still holds an open file descriptor and when it has terminated—using lsof, /proc tricks, and the extundelete utility with step‑by‑step commands.
This guide explains how to restore mistakenly removed Linux files by first checking if the deleting process still holds the file descriptor using lsof, then copying the open file from /proc, and finally using the extundelete tool when the process has already terminated.
This guide explains how to restore accidentally deleted Linux files, covering both scenarios where the file is still held open by a running process using /proc and lsof, and where the process is gone, requiring tools like extundelete with step‑by‑step commands.
This article walks through common interview questions about removing log files, demonstrates safe recursive deletion with find, explains why deleted files may still occupy space when opened, shows how to identify and clean them using lsof, logrotate, and crontab, and clarifies the differences between soft and hard links.
This guide shows how a file can appear deleted on Linux yet still occupy disk space, explains the inode reference‑count mechanism, demonstrates how to reproduce the issue with dd and a C program, and provides commands like lsof and /proc inspection to locate and release such hidden usage.
This guide explains why removing a file with rm doesn't always release space, demonstrates creating a large test file, shows how open file handles keep space occupied, and provides commands to identify and release such hidden usage.
When a huge file is removed on a Linux server but the root partition still shows 100% usage, the issue is usually caused by the file being held open by a process, reserved filesystem space, or delayed space reclamation, and can be resolved with commands like lsof, kill, or tune2fs.
This article explains how Linux file deletion works, why space may not be released when a file is removed, and shows practical commands and a C example to illustrate inode reference counting, using tools like df, dd, lsof, and proper file‑descriptor handling.
This article explains why removing a file with rm on Linux sometimes leaves disk space unchanged, demonstrates the behavior with a random file and a C program that keeps the file open, and shows how to identify and release such lingering file allocations using inode reference counts and lsof.
This guide explains how to install the lsof utility on Linux, interpret its output, filter results with grep or process IDs, handle permission limitations, and use options like +c, -i, -n, and -P to display full process names and network connections.
This guide outlines ten practical methods for Linux administrators to identify compromised machines on CentOS, including log inspection, checking /etc/passwd and /etc/shadow, analyzing login records, monitoring network traffic, and using lsof to recover deleted log files, with step‑by‑step commands and examples.
This guide outlines practical steps and command examples for Linux administrators to identify compromised machines, examine logs, verify user files, monitor login activity, capture abnormal traffic, and recover deleted logs using lsof and /proc information.
This guide shows how to quickly determine whether specific service ports are occupied on a Linux system using commands such as lsof and netstat, explains the meaning of key parameters, and provides a ready‑to‑run Python program that monitors port availability on any IP address.
This guide shows how to use Linux commands like lsof and netstat to identify occupied ports and provides a Python script that monitors specific IP ports for availability, complete with example outputs and explanations of key parameters.
This guide walks Linux operations engineers through common signs of a breached machine, showing how to examine logs, verify user files, monitor login events, use lsof for deleted files, and recover critical logs with step‑by‑step commands.
The article explains the discrepancy between the file‑handle count reported by /proc/sys/fs/file‑nr and the numbers shown by lsof, clarifying the difference between file descriptors and file handles, describing how the kernel allocates struct file objects, and showing how shared memory, mmap, and other operations can inflate handle counts unnoticed by lsof.
This guide shows how to use Linux commands such as lsof and netstat to identify occupied ports, explains the meaning of key parameters, and provides a Python script that monitors specified IP ports for availability, complete with example output.
This guide introduces the lsof utility, explains its basic usage for listing open files, demonstrates practical scenarios such as identifying files used by specific processes, checking which process occupies a port, and leveraging lsof to recover deleted files, helping administrators troubleshoot I/O and security issues.
Learn how to diagnose and alleviate heavy I/O load on Linux systems by using three essential commands—iostat for CPU and disk statistics, iotop for real‑time I/O process ranking, and lsof for listing open files—complete with key options and output interpretation.
This comprehensive guide explains how to use the powerful lsof command to list open files, inspect network connections, filter by users, processes, ports, and hosts, and apply advanced options for system monitoring and security troubleshooting on Unix-like systems.
The article explains how the Linux top command reveals filesystem cache usage, why large log files can waste cache memory, and proposes hourly log rotation with compression, using lsof to identify cached files and tools like zless to view compressed logs.
This guide explains how to use lsof and the /proc filesystem to locate open file descriptors of deleted logs or database files and restore their contents while the owning process remains active.
