When a Linux server experiences slow performance, high disk latency, or unexpected storage bottlenecks, identifying the process responsible for excessive disk I\/O becomes critical. While tools such as This guide explains how to install and use The tool works similarly to the Before installing Update the package repository and install Verify the installation:<\/p>\n Install using YUM:<\/p>\n Install using DNF:<\/p>\n Verify installation:<\/p>\n Launch You will see a real-time display showing:<\/p>\n Example:<\/p>\n Show only processes currently performing disk operations:<\/p>\n Filter activity by user:<\/p>\n Replace Generate output suitable for scripts and logging:<\/p>\n Display 10 updates and exit:<\/p>\n Show total I\/O usage since process start:<\/p>\n Run:<\/p>\n Then use interactive keys:<\/p>\n If you receive an error similar to:<\/p>\n Ensure task I\/O accounting is enabled:<\/p>\n If the output is To make the setting persistent:<\/p>\n If Whether you’re managing application servers, database hosts, or storage-intensive workloads, For detailed command options and advanced usage, refer to the manual page:<\/p>\n No. Most Linux distributions do not include Yes. Root or sudo privileges are typically required because top<\/code> and htop<\/code> help monitor CPU and memory usage, they do not provide detailed visibility into disk input\/output activity.<\/p>\niotop<\/code> is a powerful command-line utility that displays real-time disk I\/O usage by processes and users, making it easier for system administrators to troubleshoot performance issues, identify resource-intensive applications, and monitor storage activity.<\/p>\niotop<\/code> on Ubuntu, Debian, CentOS, RHEL, and other Linux distributions.<\/p>\n
\n<\/div>\nWhat is iotop?<\/h2>\n
iotop<\/code> is an interactive monitoring tool that shows:<\/p>\n\n
top<\/code> command but focuses specifically on disk I\/O operations.<\/p>\nKey Benefits<\/h3>\n
\n
\n<\/div>\nPrerequisites<\/h2>\n
iotop<\/code>, ensure:<\/p>\n\n
\n<\/div>\nInstalling iotop<\/h2>\n
Ubuntu \/ Debian<\/h3>\n
iotop<\/code>:<\/p>\nsudo apt update\nsudo apt install iotop -y<\/code><\/pre>\niotop --version<\/code><\/pre>\n
\n<\/div>\nCentOS 7 \/ RHEL 7<\/h3>\n
sudo yum install iotop -y<\/code><\/pre>\n
\n<\/div>\nCentOS Stream \/ Rocky Linux \/ AlmaLinux \/ RHEL 8+<\/h3>\n
sudo dnf install iotop -y<\/code><\/pre>\niotop --version<\/code><\/pre>\n
\n<\/div>\nRunning iotop<\/h2>\n
iotop<\/code> with root privileges:<\/p>\nsudo iotop<\/code><\/pre>\n\n
PID USER DISK READ DISK WRITE COMMAND\n2451 mysql 10.25 M\/s 1.50 M\/s mysqld\n3204 root 5.00 M\/s 2.30 M\/s rsync<\/code><\/pre>\n
\n<\/div>\nUseful iotop Commands<\/h2>\n
Display Only Active I\/O Processes<\/h3>\n
sudo iotop -o<\/code><\/pre>\n
\n<\/div>\nMonitor Specific User Activity<\/h3>\n
sudo iotop -u mysql<\/code><\/pre>\nmysql<\/code> with the required username.<\/p>\n
\n<\/div>\nBatch Mode Output<\/h3>\n
sudo iotop -b<\/code><\/pre>\n
\n<\/div>\nCapture Limited Iterations<\/h3>\n
sudo iotop -b -n 10<\/code><\/pre>\n
\n<\/div>\nDisplay Accumulated I\/O Statistics<\/h3>\n
sudo iotop -a<\/code><\/pre>\n
\n<\/div>\nSort Processes by I\/O Usage<\/h3>\n
sudo iotop<\/code><\/pre>\n\n
r<\/code> \u2013 Sort by read activity<\/li>\nw<\/code> \u2013 Sort by write activity<\/li>\no<\/code> \u2013 Toggle active I\/O processes only<\/li>\na<\/code> \u2013 Toggle accumulated I\/O mode<\/li>\nq<\/code> \u2013 Quit<\/li>\n<\/ul>\n
\n<\/div>\nTroubleshooting<\/h2>\n
“Netlink error: No such file or directory”<\/h3>\n
Netlink error: No such file or directory<\/code><\/pre>\ncat \/proc\/sys\/kernel\/task_delayacct<\/code><\/pre>\n0<\/code>, enable it:<\/p>\nsudo sysctl kernel.task_delayacct=1<\/code><\/pre>\necho \"kernel.task_delayacct=1\" | sudo tee -a \/etc\/sysctl.conf\nsudo sysctl -p<\/code><\/pre>\n
\n<\/div>\nAlternative Tools<\/h2>\n
iotop<\/code> is unavailable, consider these alternatives:<\/p>\n\n\n
\n Tool<\/th>\n Purpose<\/th>\n<\/tr>\n \n iostat<\/td>\n Disk utilization statistics<\/td>\n<\/tr>\n \n dstat<\/td>\n System resource monitoring<\/td>\n<\/tr>\n \n atop<\/td>\n Advanced system monitoring<\/td>\n<\/tr>\n \n sar<\/td>\n Historical performance analysis<\/td>\n<\/tr>\n \n pidstat<\/td>\n Per-process resource statistics<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n<\/div>\nConclusion<\/h2>\n
iotop<\/code> is an essential monitoring tool for Linux administrators and DevOps engineers who need visibility into disk I\/O activity. It provides real-time insights into which processes and users are consuming storage resources, helping quickly identify performance bottlenecks and troubleshoot system slowdowns.<\/p>\niotop<\/code> offers a simple and effective way to monitor disk usage and maintain optimal system performance.<\/p>\nman iotop<\/code><\/pre>\n
\n<\/div>\nFrequently Asked Questions (FAQ)<\/h2>\n
1. What is iotop used for?<\/h3>\n
iotop<\/code> is a Linux monitoring utility that displays real-time disk I\/O usage by processes and users. It helps administrators identify applications or services causing high disk read\/write activity.<\/p>\n
\n<\/div>\n2. Is iotop installed by default on Linux?<\/h3>\n
iotop<\/code> by default. It must be installed manually using the package manager (apt<\/code>, yum<\/code>, or dnf<\/code>).<\/p>\n
\n<\/div>\n3. Do I need root privileges to run iotop?<\/h3>\n
iotop<\/code> needs access to kernel-level I\/O statistics.<\/p>\nsudo iotop\n<\/code><\/pre>\n
\n<\/div>\n<\/code><\/pre>\nRelated Articles<\/h2>\n
<\/code><\/pre>\n