Red Hat Bugzilla – Bug 1290948
transferring files of samba shares through "Browse Network" of Nautilus is SLOW
Last modified: 2017-07-25 16:15:14 EDT
Description of problem:
Accessing a samba share through the "Browse Network" feature of Nautilus and copying a file results in terrible transfer speeds.
Version-Release number of selected component (if applicable): 3.16.2
How reproducible: Highly
Steps to Reproduce:
1. Browse Network through Nautilus to some samba share
2. Right click the file and copy
3. Paste the file somewhere locally
Actual results: Transfer speeds will be terrible, 51MB/s
Expected results: Transfer speeds should be much higher, 100MB/s or more for me...
(Tests were done with very large files, 3.8-4.5GB, and a different file each time to avoid caching)
- Transferring via scp without compression: 100MB/s
- Transferring via smbclient "get": 104MB/s
- Transferring via manual CIFS mount (terminal): 110MB/s
- Transferring via manual CIFS mount using nautilus: 116MB/s
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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
Thank you for reporting this bug and we are sorry it could not be fixed.
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 24 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.