[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#309405: marked as done (mount.cifs: poor performance and high CPU load with large files (500MB+) compared to mount.smbfs)



Your message dated Tue, 4 Jun 2013 00:29:27 +0200
with message-id <20130603222926.GC5604@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #309405,
regarding mount.cifs: poor performance and high CPU load with large files (500MB+) compared to mount.smbfs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
309405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=309405
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: smbfs
Version: 3.0.14a-1
Severity: normal


I run a Linux box within a VMware, a Windows Server 2003 and a
Windows 2000 Server (both not in VMware).
When copying a CD image file from within Linux to a cifs mounted
Win2003 share, I see a very poor performance and high CPU load
(about 90% system) on the Linux VM.
Copying begins with 3 MB/s (measured by mc), after 4% it suddenly stops
for say 10-20 seconds, then continues with 1..2 MB/s, but stopping
from time to time for several seconds. CPU load is only high while copying,
not in the pauses. Copying the whole file (700MB) took about 10 minutes.

Copying the same file in the same direction from a samba share
at the W2K3 box is very much faster, copying is finished in about a minute,
and CPU load on the Linux side is by far less.

When copying the same file from Linux to a cifs mounted Windows 2000
share, I get a similar picture: Copying begins with 3 MB/s, but soon slows
down to 1 MB/s with high CPU load. But here, it doesn't seem to have these
long idle times. Nevertheless copying takes about 10 minutes, too.

When mounting the Win2000 share with smbfs, however, I get about 4 MB/s
and a system load of approx. 35%. (This may indicate, that bug #203887
is indeed solved.)


I don't think it has anything to do with VMware as all other transfers
from and to this Linux VM are fast (NFS, HTTP, FTP, and Samba as mentioned).
(FTP and NFS copy performs with 10 MB/s)

I tried to compile a new kernel with the newest CIFS (1.34), but unfortunately
it doesn't compile with the Debian sarge kernel sources for 2.6.8,
neither plain 1.34 nor 1.34-RHEL4.

CIFS 1.34 does compile with Debian sid kernel 2.6.11, but unfortunately,
the VMware net driver doesn't work with this kernel, so I cannot test this.

I cannot test smbfs with W2K3 for comparison either, as I don't want to modify
the W2K3 settings to allow non-signed SMB.

On the Linux side I could test nearly everything, however, if somebody has
some more ideas what to test.


Martin


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-vmware-1 (from sarge kernel-source-2.6.8-15)
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

Versions of packages smbfs depends on:
ii  libc6                       2.3.2.ds1-21 GNU C Library: Shared libraries an
ii  libcomerr2                  1.37-2       common error description library
ii  libkrb53                    1.3.6-2      MIT Kerberos runtime libraries
ii  libldap2                    2.1.30-6     OpenLDAP libraries
ii  netbase                     4.21         Basic TCP/IP networking system
ii  samba-common                3.0.14a-1    Samba common files used by both th

-- no debconf information


--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.0 / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---

Reply to: