Description of problem: No disk activity in gnome-system-monitor panel icon. I have LVM set on several software RAID-5 partitions. That functionality worked fine on Fedora8 installation. Version-Release number of selected component (if applicable): How reproducible: Copy file to/from the disk or create long disk activity such as updatedb. Observe no indication in disk section of the monitor. Steps to Reproduce: 1. 2. 3. Actual results: Black window in disk section. Expected results: See read and write activities. Additional info:
[alex@htpc ~]$ uname -r 2.6.27.4-68.fc10.i686
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
two F10 systems; System Monitor 2.24.3.1 -- disk activity absent; System Monitor 2.24.2 -- disk activity present. I'm updating the second system and expect to see the disk activity disappear as on the first system.
Same problem here on F10, 2.6.27.21-170.2.56.fc10.x86_64 with gnome-system-monitor-2.24.3-1.fc10.x86_64. Disk usage on root file system (/dev/sda6 on / type ext3) works fine, but LVM volumes (e.g. /dev/mapper/home-home on /home type ext3) don't show up in disk usage (system monitor applet).
I have the same problem on FC11. here is what I have installed [adler@office01 vpnclient]$ rpm -qa | grep -i system-monitor gnome-system-monitor-2.26.1-2.fc11.x86_64 [adler@office01 vpnclient]$ rpm -qa | grep -i kernel kernel-headers-2.6.30.5-43.fc11.x86_64 kernel-firmware-2.6.30.5-43.fc11.noarch kerneloops-0.12-5.fc11.x86_64 kernel-2.6.29.6-217.2.8.fc11.x86_64 kernel-2.6.29.6-217.2.16.fc11.x86_64 kernel-devel-2.6.30.5-43.fc11.x86_64 kernel-devel-2.6.29.6-217.2.16.fc11.x86_64 kernel-devel-2.6.29.6-217.2.8.fc11.x86_64 kernel-2.6.30.5-43.fc11.x86_64 [adler@office01 vpnclient]$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/md0 50394884 11395136 36439796 24% / /dev/sda1 194442 34286 150117 19% /boot /dev/md1 426094448 195737520 208712560 49% /export/home tmpfs 4056712 44112 4012600 2% /dev/shm notice that I have / and /export/home mounted on /dev/mdX devices. when I do IO to /boot, the system disk monitor lights up!
After moving to FC11, where I had to get rid of LVM since the system won't boot, so I left with only raid-5 and raid-1, there is still no disk activity in the monitor.
This issue still exists in FC12. Is anybody out there? This must affect plenty of users.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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
Please bump this defect report to F12. Same problem exists there.
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.
See bug 608948.