Created attachment 1306321 [details] Screenshot of files being moved and monitor's display Description of problem: Running the monitor app on a gigabit Ethernet connection gives ridiculous statistics on the rate of transfer. Version-Release number of selected component (if applicable): gnome-system-monitor-3.24.0-1.fc26.x86_64 How reproducible: I'm running Monitor on a box that is being used as the source of a 650GB transfer of thousands of files via rsync to a backup server. Monitor's statistics and graph are orders of magnitude understated. The screen snapshot should be referenced. What it shows is the Monitor screen overlayed upon an lsof output of the files currently in process. These files are almost all in the 1GB range as they are video (movie) files. The following lsof is used: lsof -p 8804 -r |grep billlaptop and this command refreshes the display (-r) every 15 seconds. As can be seen, these large files are being processed and yet the monitor screen shows some piddling throughput statistics. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional Information: bill@billlaptop ~$ ethtool ens5 Settings for ens5: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: No Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Cannot get wake-on-lan settings: Operation not permitted Current message level: 0x0000003f (63) drv probe link timer ifdown ifup Link detected: yes root@rackmount billlaptop# lspci|grep -i ethernet 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 EOL if it remains open with a Fedora 'version' of '26'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.