This guide shows you how to determine whether a disk is busy in Linux, which is essential for diagnosing slow performance, spotting I/O bottlenecks, and verifying that backups or large transfers are actually progressing. You’ll learn to use built-in command-line tools that report disk activity in real time, and how to interpret their output.
What You’ll Need
- A Linux system with a terminal (any distribution works).
- Basic familiarity with the command line.
- Root or sudo access (required for some tools like
iostatto show all devices).
Step-by-Step
- Open a terminal. Press
Ctrl+Alt+Tor find “Terminal” in your applications menu. - Check if the
sysstatpackage is installed. Runwhich iostat. If it returns a path (e.g.,/usr/bin/iostat), you’re ready. If not, install it: on Debian/Ubuntu usesudo apt install sysstat; on Fedora/RHEL usesudo dnf install sysstat. - Use
iostatto see disk utilization. Runiostat -x 1 3. This shows extended statistics every second for 3 samples. Look at the%utilcolumn. A value near 100% means the disk is heavily busy; values below 50% indicate moderate activity. Theawaitcolumn (average I/O time in milliseconds) also helps: higher values suggest queuing. - Use
vmstatfor a quick system-wide view. Runvmstat 1 5. Look at thebi(blocks in) andbo(blocks out) columns. Non-zero values indicate disk I/O is happening. Thewacolumn (I/O wait time) shows the percentage of CPU time waiting for I/O; high values (e.g., >20%) often mean the disk is a bottleneck. - Use
iotopto see which processes are using the disk. Runsudo iotop. This interactive tool shows a list of processes with their I/O read/write rates. Pressqto quit. Ifiotopis not installed, install it with your package manager (e.g.,sudo apt install iotop). - Use
pidstatfor per-process I/O (from sysstat). Runpidstat -d 1 5. TheKB_rd/sandKB_wr/scolumns show read/write rates per process. This helps identify which application is causing the disk activity. - Check the kernel I/O counters. Run
cat /proc/diskstats. This shows raw counters for each disk. Look at fields 6 (reads completed) and 10 (writes completed). If these numbers are increasing rapidly when you sample twice, the disk is busy. - Use
dstatfor a combined view (if installed). Rundstat -d 1 5. This shows disk read/write totals per second. If both are zero, the disk is idle.
Common Mistakes
- Misreading
%utilas a percentage of capacity.%utilis the percentage of time the disk was busy serving requests, not how full it is. A disk can be 10% full but 100% busy. - Forgetting that
iostatshows averages since boot unless you specify an interval. Without a delay argument,iostatshows cumulative averages, which may hide current spikes. Always useiostat 1or similar to get live data. - Ignoring the difference between a single disk and a RAID array. On RAID,
iostatmay show each member disk separately. The%utilof the array device (e.g.,md0) is more relevant for overall performance. - Using
topto check disk I/O.topdoes not show disk I/O by default. Useiotoporpidstatinstead.
Tips
- Combine tools: start with
vmstatto see if I/O is happening, then useiotopto find the culprit process. - For a specific disk, use
iostat -x /dev/sda 1(replacesdawith your device) to focus on that disk only. - Use
watch -n 1 'iostat -x 1 1'to get a continuously updating view. - If you see high
awaitbut low%util, the disk may be suffering from many small random I/O requests rather than being saturated. - Remember that SSDs and HDDs have different expected
awaitvalues; an SSD withawaitof 10ms is slow, while an HDD might be fine.
Troubleshooting
- If
iostatshows “command not found”, install sysstat as described in Step 2. If you cannot install it, usevmstatand/proc/diskstatsinstead. - If
iotoprequires root and you don’t have sudo, you can usepidstat -d(if sysstat is installed) without root, but it may only show your own processes. Alternatively, runsudo -ito get a root shell if you know the root password. - If
vmstatshows all zeros even when you’re copying a large file, the file may be served from cache (page cache). Usesyncto force writes to disk, or usedd if=/dev/zero of=/tmp/test bs=1M count=1024 conv=fdatasyncto generate real I/O. - If
%utilstays at 100% but the system feels fast, you might be looking at a virtual disk (like a cloud volume) that reports 100% due to virtualization overhead. Cross-check withvmstatwa; if it’s low, the disk may not actually be a bottleneck. - If you need to see historical data, use
sar(from sysstat) withsar -d 1to collect samples over time, then review later.
Frequently Asked Questions
What does “busy” mean for a disk?
It means the disk is actively processing I/O requests. A disk can be busy even if it’s not transferring data at full speed, for example when seeking on an HDD.
Is %util from iostat the same as disk usage?
No. %util is the percentage of time the disk was busy during the sample interval. Disk usage refers to how much storage space is used.
Can I check disk busyness without root?
Yes. vmstat and iostat (without the -x flag) often work without root. iotop requires root, but pidstat -d may work for your own processes.
Why does iostat show multiple devices?
It lists all block devices, including partitions and logical volumes. Use iostat -x /dev/sda to filter to a specific device.
How do I tell if a disk is busy due to reads or writes?
Look at the rkB/s and wkB/s columns in iostat output. If reads dominate, the disk is busy reading; if writes dominate, it’s writing.
What is a normal %util value?
For a healthy system, %util below 50% is generally fine. Sustained values above 80% indicate the disk is likely a performance bottleneck.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- How to Create App Shortcuts in Windows 10 Start Menu
- How to Rename a SQL Server Database
- Recover Deleted Admin Account in Windows 11
- Install Custom Recovery on Samsung Galaxy E5
- Fix Administrator Blocked You From Running This App Error
- Fix Google Calendar Not Syncing on iPhone