Bug#742642: iotop reports gnome-shell I/O% but no disk I/O being done

2014-04-19 Thread Paul Wise
On Tue, 2014-03-25 at 16:59 -0400, Dominique Brazziel wrote:

 I think this may be a quirk (or maybe bug) in the netlink/taskstats interface
 where Unix socket I/O is being counted as block I/O.  I will try and write a
 test program to loop doing socket I/O and see if iotop shows it doing a % of
 I/O.

Did you manage to complete this test program?

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part


Bug#742642: iotop reports gnome-shell I/O% but no disk I/O being done

2014-04-07 Thread Paul Wise
On Tue, 2014-03-25 at 16:59 -0400, Dominique Brazziel wrote:

 I think this may be a quirk (or maybe bug) in the netlink/taskstats interface
 where Unix socket I/O is being counted as block I/O.  I will try and write a
 test program to loop doing socket I/O and see if iotop shows it doing a % of
 I/O.

Indeed, doesn't sound like a bug in iotop but in the Linux kernel to me.

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part


Bug#742642: iotop reports gnome-shell I/O% but no disk I/O being done

2014-03-25 Thread Dominique Brazziel
Package: iotop
Version: 0.6-1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
iotop -o shows gnome-shell doing I/O (non-zero '%I/O' value) when in fact
no disk I/O is being done by gnome-shell.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
ran iotop -o to show tasks doing current I/O
   * What was the outcome of this action?
A few threads show up in each screen, with gnome-shell consistently showing
at or near the top of the '%I/O' column, but no disk I/O was shown in the top
summary or any of the individual process lines.
   * What outcome did you expect instead?
Investigation of the gnome-shell process via strace and /proc/pid/fd showed
the recvmsg and writev I/O being done to Unix sockets, not files on disk.

I think this may be a quirk (or maybe bug) in the netlink/taskstats interface
where Unix socket I/O is being counted as block I/O.  I will try and write a
test program to loop doing socket I/O and see if iotop shows it doing a % of
I/O.

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.13.5-1inter04-686-pae (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages iotop depends on:
ii  python  2.7.5-5

iotop recommends no packages.

iotop suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org