On Mon, Mar 14, 2011 at 9:18 AM, Maier, Uwe wrote:
> When you compare that to "top" I must say that my top (part of procps 3.2.8)
> /does/ deliver values on the first shot. Even with "top -d 3600".
Yes, so does iotop.
The difference is that top's values are not 0 on the first shot and
that's bec
aume Chazarain [mailto:guic...@gmail.com]
> Sent: Montag, 14. März 2011 02:49
> To: 614...@bugs.debian.org
> Subject: Bug#614978: iotop: All values 0.0 when using -b parameter
>
> iotop's scraping loop looks like:
>
> read_counters()
> while running:
> read_coun
iotop's scraping loop looks like:
read_counters()
while running:
read_counters()
print delta
sleep(delay)
So there are indeed two reads close to each other at startup.
You can see the first read in
http://repo.or.cz/w/iotop.git/blob/HEAD:/iotop/data.py#l372:
372 # A first time as
1 06:15
> To: Maier, Uwe; 614...@bugs.debian.org
> Cc: Guillaume Chazarain
> Subject: Re: Bug#614978: iotop: All values 0.0 when using -b parameter
>
> On Fri, 2011-02-25 at 13:14 +, Maier, Uwe wrote:
>
> > Hi Paul,
> > a.) fails here too
> > b.) fails here
> &g
On Fri, 2011-02-25 at 13:14 +, Maier, Uwe wrote:
> Hi Paul,
> a.) fails here too
> b.) fails here
> c.) fails here
>
> Seems your system is different than mine (smp?).
I have a 4-core Intel i7 processor, you seems to have many more
processors than I do.
Guillaume, is the number of CPUs like
g
> Subject: RE: Bug#614978: iotop: All values 0.0 when using -b parameter
>
> On Fri, 2011-02-25 at 08:04 +, Maier, Uwe wrote:
>
> > During the execution of your request I stumbled upon the following
> output:
> ...
>
> I can reproduce that with this:
>
> t
On Fri, 2011-02-25 at 08:04 +, Maier, Uwe wrote:
> During the execution of your request I stumbled upon the following output:
...
I can reproduce that with this:
terminal 1: $ cat /dev/zero > foo & sleep 10s ; kill %1 ; rm -f foo
terminal 2: $ iotop -b | grep 'cat /dev' | grep -v grep
12706
ian.org
> Cc: control
> Subject: Re: Bug#614978: iotop: All values 0.0 when using -b parameter
>
> tags 614978 + unreproducible moreinfo
> thanks
>
> On Thu, 2011-02-24 at 16:34 +, Maier, Uwe wrote:
>
> > When using the -b parameter which should enable the ba
tags 614978 + unreproducible moreinfo
thanks
On Thu, 2011-02-24 at 16:34 +, Maier, Uwe wrote:
> When using the -b parameter which should enable the batch mode every
> value is reset to 0.0 .
It works for me, are you sure your system is doing some I/O? Try running
"cat /dev/zero > foo & sleep
Package: iotop
Version: 0.4-2
iotop works fine here.
Most values are zeros, but they are true (at least in my case).
OP: Have you tried `iotop -bo`? It prevents reporting threads that don't use
disk, so the output is not cluttered with entries of zero values.
Also there's a simple test:
`dd if=/
Package: iotop
Version: 0.4-2
Severity: normal
When using the -b parameter which should enable the batch mode every value is
reset to 0.0 .
Adding other parameters like -P, -a, -n, -k do not change anything.
Saving the output of iotop without -b to a file (containing all the control
characters)
11 matches
Mail list logo
