After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 586853 - gnome-system-monitor does not display hd reads to dmraid or mdadm
gnome-system-monitor does not display hd reads to dmraid or mdadm
Status: RESOLVED DUPLICATE of bug 160441
Product: system-monitor
Classification: Core
Component: general
unspecified
Other All
: Normal major
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2009-06-24 15:04 UTC by Fermulator
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Fermulator 2009-06-24 15:04:41 UTC
Please describe the problem:
This is a forwarded bug from the Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/126618

As confirmed by the above bug reports, the gnome-system-monitor applet which display hard disk activity does not display activity for dmraid (fake raid) or mdadm (software raid).

Steps to reproduce:
1. Install Ubuntu 9.04 on a system with "fake raid" (dmraid) or "software raid" (mdadm).
2. Add the gnome-system-monitor applet to the main panel.
3. Right click on the applet, and select "Properties".
4. Choose "Hard Disk".

Perform some hard drive intense operation.  (i.e. copy a large file from /dev/sda1 to /dev/sda1)

Actual results:
The hard disk activity monitor will not display any activity for mdadm or dmraid devices!

Expected results:
The hard disk activity monitor should display said activity.

Does this happen every time?
Yes.

Other information:
The hard disk activity monitor works 100% correctly and as expected for regular IDE and SATA disk drives.
Comment 1 Fermulator 2009-06-24 15:05:45 UTC
NOTE: Bugzilla doesn't appear to have the latest version in the drop down, so I selected "unspecified".  The version is "System Monitor 2.26.01".
Comment 2 tru ell 2009-07-01 21:54:40 UTC
I confirm that this is an old bug which does not seem to get fixed since the developers of System Monitor don't seem to use fake raid. Anyway, my few cents:

Binary package hint: gnome-system-monitor

Ubuntu 6.10: I was using gnome-system-monitor in an environment installed on a normally mounted drive (/dev/sda1) and at that time it correctly displayed
disc reads and writes to the filesystem (I have used green color for read, and red color for write).

But since my move to a fake-raid system (raid 0: dmraid using two 400GB SATA-II drives on a promise fasttrack controller) only writes are now displayed.
The root filesystem is now mounted on /dev/mapper/pdc_cichcdiia.
Comment 3 Benoît Dejean 2009-07-01 22:32:05 UTC
It's not that i don't care. There's the same problem with LVM. The kernel doesn't report per partition statistics with these kind of IO.

*** This bug has been marked as a duplicate of 160441 ***
Comment 4 tru ell 2009-07-02 10:17:10 UTC
> The kernel doesn't report per partition statistics with these kind of IO.

That is NOT true. Read access IS displayed in my installation of System Monitor. I was talking about that only the *write* access is not displayed.

The point is: if the System Monitor can display read access, what's the problem with the write access?

Because of that I don't think it is correct to just set it to duplicate.
Comment 5 Fermulator 2009-07-16 19:17:04 UTC
I don't see either read OR write ...
Comment 6 LAZA 2010-06-12 16:34:05 UTC
I think this is the same bug:

On my installation of Lucid I only see read/write processes on root-Partition (sda7), not from /home!
/home is a LVM over sdb and sdc.

$ sudo fdisk -l

Platte /dev/sda: 1500.3 GByte, 1500301910016 Byte
255 Köpfe, 63 Sektoren/Spur, 182401 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00094521

   Gerät  boot.     Anfang        Ende     Blöcke   Id  System
/dev/sda1               1        4177    33551721    7  HPFS/NTFS
Partition 1 endet nicht an einer Zylindergrenze.
/dev/sda2            4178        4438     2096482+  82  Linux Swap / Solaris
/dev/sda3   *        4439      182401  1429487767    5  Erweiterte
/dev/sda5            4439        5482     8385898+  83  Linux
/dev/sda6            5483        6526     8385898+  83  Linux
/dev/sda7            6527        7570     8385898+  83  Linux
/dev/sda8            7571      182401  1404329976    7  HPFS/NTFS

Platte /dev/sdb: 1000.2 GByte, 1000204886016 Byte
255 Köpfe, 63 Sektoren/Spur, 121601 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000da868

   Gerät  boot.     Anfang        Ende     Blöcke   Id  System
/dev/sdb1   *           1      121601   976760001   8e  Linux LVM

Platte /dev/sdc: 1000.2 GByte, 1000204886016 Byte
255 Köpfe, 63 Sektoren/Spur, 121601 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00001dbc

   Gerät  boot.     Anfang        Ende     Blöcke   Id  System
/dev/sdc1   *           1      121601   976760001   8e  Linux LVM

Platte /dev/sdd: 640.1 GByte, 640135028736 Byte
255 Köpfe, 63 Sektoren/Spur, 77825 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000882d6

   Gerät  boot.     Anfang        Ende     Blöcke   Id  System
/dev/sdd1               1          16      128488+   b  W95 FAT32
/dev/sdd2              17       77825   625000792+   7  HPFS/NTFS

Platte /dev/sde: 1500.3 GByte, 1500301910016 Byte
255 Köpfe, 63 Sektoren/Spur, 182401 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0006a300

   Gerät  boot.     Anfang        Ende     Blöcke   Id  System
/dev/sde1               1       16709   134215011   83  Linux
/dev/sde2           16710      182401  1330920990    7  HPFS/NTFS



~$ uname -a
Linux Lucid 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 19:31:57 UTC 2010 x86_64 GNU/Linux

gnome-system-monitor 2.28.0-1ubuntu2