On 27.02.2017 07:15, Paul Wise wrote:
On Sun, 2017-02-26 at 11:18 +0100, Frank Breitling wrote:
I didn't mean that it does not show any write access.
But some gets lost.
I see this problem in a long term monitoring with low disk activity.
Do you have any examples of situations where you see th
On Sun, 2017-02-26 at 11:18 +0100, Frank Breitling wrote:
> I didn't mean that it does not show any write access.
> But some gets lost.
> I see this problem in a long term monitoring with low disk activity.
Do you have any examples of situations where you see this issue?
Please list the exact com
I didn't mean that it does not show any write access.
But some gets lost.
I see this problem in a long term monitoring with low disk activity.
The interactive mode is not useful for this, since its entries disappear.
On 26.02.2017 11:08, Paul Wise wrote:
On Sun, 2017-02-26 at 10:48 +0100, Fran
On Sun, 2017-02-26 at 10:48 +0100, Frank Breitling wrote:
> It seems like iotop does not report the write access correctly.
I cannot reproduce this.
Please try this:
sudo iotop -bktoqqqd 5
dd count=1024 bs=1M if=/dev/zero of=bar
rm -f bar
> sudo iotop -bktoqqqd 5
Do you have the same issue in
Package: iotop
Version: 0.6-2
Severity: normal
Dear Maintainer,
I monitored my hard disk write access with
sudo iotop -bktoqqqd 5
and
iostat -dzp 5
While iotop returns
Device:tpskB_read/skB_wrtn/skB_readkB_wrtn
sdb 1.60 0.00 8.78
5 matches
Mail list logo
