New answers tagged io
I think that the easiest solution is to "see" the local file system (or a part of it) on the server. For instance, you can use SSHFS.
512 byte is not really the default sector size. It depends on you hardware. You can display what physical/logical sector sizes your disk reports via the /sys pseudo filesystem, e.g.: # cat /sys/block/sda/queue/physical_block_size 4096 # cat /sys/block/sda/queue/logical_block_size 512 What is the difference between those two values? The ...
No, it is not possible, nor would it matter if it were. IO is typically done in units of at least 4096 bytes anyhow, and usually much more.
A new tool is now available to inspect already running processes files access, display progress and throughput estimation: https://github.com/Xfennec/cv If your somecommand or anothercommand are already known by cv, it is just as easy to use as watch cv -wq, or else you have to use -c option to monitor specifically your processes.
The man page of iostat says: The interval parameter specifies the amount of time in seconds between each report. The first report contains statistics for the time since system startup (boot), unless the -y option is used (in this case, this report is omitted). Each subsequent report contains statistics collected during the interval ...
Your iostat -dx 1 will not terminate and continuously report values. (The 1 refers to the interval to to the count.) You probably want something like io_load=$(iostat -dx) echo "$io_load"
Top 50 recent answers are included