NFS and SMB transfers across LAN work very slowly

Bug #49819 reported by MrAuer
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

In Dapper final release, both SMB and NFS mounts accessed across LAN (100mbit ethernet) transfer data at about 1/10 rate of what it should be. Meaning a transfer rate of 300-700 kilos/sec, when it normally is closer to 10 megabytes.

The problem is there with both Samba and NFS, first noticed it with Samba. This problem shows up in 3 different machines, 2 desktops, 1 old Thinkpad. All of these machines worked correctly when running under Hoary, but 2 of them also had this problem with SMB/Breezy packages. Also, the problem persists in file transfers between Win/Apple systems, which also worked fine previously. All 3 boxes are clean Dapper LTS installs. Verified that the hardware works: Transfers across LAN using HTTP protocol work at near the 100 mbps limit, around 9 megs/sec.

Revision history for this message
Mark (nix4me) wrote :

I also have confimed this problem. NFS transfer between my 2 dapper machines are at around 3-400K. HTTP transfer is at 9.8M.

Mark

Revision history for this message
MrAuer (kari-jussila) wrote :

Today I reinstalled and reconfigured all Samba components (samba-common, samba, smbfs), and the problem persists still. Sometimes speed goes up to 3-5 megs one way, but still works slowly moving files the other way around (ie. when I move stuff from box 1 to box 2, its slow, but when moving files from box 2 to 1 it works faster. Both boxes are configured identically)

Revision history for this message
MrAuer (kari-jussila) wrote :

Now I also installed SSH server on both boxes, and tried moving files with both scp and the Nautilus interface. SSH transfers on LAN work at the same slow speed as SMB and NFS, so only HTTP protocol seems to utilize full ethernet speed. Im at a loss to explain what might cause it. Ive also disabled IPv6, no effect. Next im thinking of trying some other distribution on the other box to see if the problem persists when the other box runs something else than Dapper.

Revision history for this message
Caroline Ford (secretlondon) wrote :

-> Confirmed (other commentors have confirmed)

Revision history for this message
Caroline Ford (secretlondon) wrote :

->netcfg (which may be the wrong networking package)

Revision history for this message
Colin Watson (cjwatson) wrote :

Caroline, netcfg is part of the installer and not likely to be relevant here. I'm reassigning to the kernel, which is probably a better bet.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
MillenniumBug (millenniumbug) wrote :

This bug report concerns only obsolete releases of Ubuntu. Is it still relevant?

Revision history for this message
MillenniumBug (millenniumbug) wrote :

Closing this bug report due to obsolete versions and lack of activity.

If a similar bug appears in Ubuntu 10.10, please open a new report.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
mmm (kontakt-podvodnik) wrote :

Well i have quite fresh installation of Ubuntu 10.04 LTS and i am having the same problem. When i test network performance between server and client using the iperf tool both UDP and TCP shows speeds close to 100mpbs (slightly over 9MBps). When i try to copy larger file using NFS it has constant transfer around 700kbps.

Changed in linux (Ubuntu):
status: Invalid → New
Revision history for this message
mmm (kontakt-podvodnik) wrote :

I tried to copy the file through NFS using Krusader and also MC.

When i try to copy the same file using ssh/fish in Krusader i get speed around 2.5MB/s.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi MrAuer,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 49819

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.