Red Hat Bugzilla – Bug 1476490
Inaccurate Monitor graph and statistics
Last modified: 2018-05-03 04:31:41 EDT
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):
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:
bill@billlaptop ~$ ethtool ens5
Settings for ens5:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 1000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: No
Port: Twisted Pair
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'
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.