Iotop-op
-H,--help Show help and then exit
-O,--only shows only the process or thread that is generating I/O. In addition to the parameters, you can press O to take effect during the run.
-B,--batch non-interactive mode, typically used to log logs
-N NUM,--iter=num set the number of monitoring, the default is unlimited. Useful in non-interactive mode
-D SEC,--delay=sec sets the interval for each monitor, defaults to 1 seconds, accepts non-shaping data such as 1.1
-P PID,--pid=pid specifies the monitored process/thread
-u user,--user=user specifies to monitor the I/O generated by a user
-P,--processes show only processes, default Iotop show All Threads
-A,--accumulated shows cumulative I/O, not bandwidth
-K,--kilobytes uses KB units instead of human-friendly units. Script programming is useful in non-interactive mode.
-T,--time plus timestamp, non-interactive non-modal.
-Q,--quiet prohibits the first few lines, non-interactive mode. There are three ways of specifying it.
-q Displays column names only on first monitoring
-QQ never display column names.
-QQQ never displays I/O rollups.
A strange situation has come up today.
XX bucket landlord Io is very high, each time it lasts 1 minutes, according to experience may be the Redis write-back, the results confirmed that it is true, but with iotop-op but not see any redis shadow. Later instead of counting the accumulated IO, I finally see the following command
Iotop-opa
Total DISK read:458.27 k/s | Total DISK write:12.65/s
PID PRIO USER disk READ disk write> swapin IO COMMAND
6212 BE/4 root 40.00 K 619.76 M 99.99% 99.99% redis-server XXX
6213 BE/4 root 0.00 B 436.88 M -33275.58 64.67% xxx
Use Iotop to see exactly which process is consuming IO