Bug 477340

Summary: system monitor applet does not display disk IO for /dev/md0 devices
Product: [Fedora] Fedora Reporter: Stephen Adler <adler>
Component: gnome-appletsAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 10CC: adler, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-18 07:21:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
my fstab if it helps. none

Description Stephen Adler 2008-12-20 18:24:40 UTC
Created attachment 327549 [details]
my fstab if it helps.

Description of problem:

My system is configured with software raid 1 mirroring and the disk IO does not show up in the disk IO monitor of the system monitor applet.

Version-Release number of selected component (if applicable):

fedora 10


How reproducible:

every time


Steps to Reproduce:
Configure you system to have software raid disk devices.
  
Actual results:

The system monitor disk IO plots are always recording 0 IO. The usb disk IO is plotted (i.e. non-zero) For example, when I plug my FS100 cannon cam corder into my system over USB, and copy the video files off the cam corder, you see the system monitor disk IO plots show data transfer. I have another system which has regular ext3 formatted disks (i.e. non raid or logical volumed) and you see the disk IO on that system. (it's also fedora 10)


Expected results:

System monitor should show disk IO Activity when I read and write files to my disk.

Additional info:

It used to work fine on fedora 8.

Comment 1 Bug Zapper 2009-11-18 12:41:59 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2009-12-18 07:21:01 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.