Ubuntu 13.10 Samba Server sehr langsam

sanjiblubbl

Ensign
Registriert
Jan. 2012
Beiträge
215
Hey Leute,

ich hatte heute ein paar Daten von meinem Server auf meinen Rechner (Win 7) kopieren wollen und dabei festgestellt, dass ich mit ca. 10 mb/s kopiert hatte. Normalerweise kopiere ich zwischen 80-110 mb/s auf die PC's/ Laptop's.

Schreiben ist kein problem, da habe ich im durschnitt 97 mb/s.

Ich habe es an mehreren Rechnern via Samba getestet. 2 PC's & 3 Laptop's (davon einer mit Kubuntu)

Ich hatte die letzten Tage nur ein paar Paketupdates gemacht und ein System upgrade (kleineres, war zuvor schon 13.10)


Daraufhin hatte ich einige Speed Test über Netzlaufwerke gemacht. Leider genauso ernüchternd, mit ca. 8-10 mb/s lesen und ca. 120 mb/s schreiben.(siehe bild unten)


Hier ein Auszug via Konsole mit HDParm

Code:
/dev/sda:
 Timing O_DIRECT cached reads:   752 MB in  2.00 seconds = 375.62 MB/sec
 Timing O_DIRECT disk reads: 1380 MB in  3.00 seconds = 459.31 MB/sec

/dev/sdb:
 Timing O_DIRECT cached reads:   386 MB in  2.01 seconds = 192.25 MB/sec
 Timing O_DIRECT disk reads: 554 MB in  3.00 seconds = 184.42 MB/sec

/dev/sdc:
 Timing O_DIRECT cached reads:   384 MB in  2.01 seconds = 191.23 MB/sec
 Timing O_DIRECT disk reads: 534 MB in  3.01 seconds = 177.66 MB/sec

/dev/sdd:
 Timing O_DIRECT cached reads:   236 MB in  2.01 seconds = 117.66 MB/sec
 Timing O_DIRECT disk reads: 364 MB in  3.01 seconds = 120.83 MB/sec

/dev/sde:
 Timing O_DIRECT cached reads:   242 MB in  2.01 seconds = 120.11 MB/sec
 Timing O_DIRECT disk reads: 494 MB in  3.00 seconds = 164.47 MB/sec

/dev/sdf:
 Timing O_DIRECT cached reads:   686 MB in  2.00 seconds = 342.22 MB/sec
 Timing O_DIRECT disk reads: 378 MB in  3.01 seconds = 125.56 MB/sec

/dev/sdg:
 Timing O_DIRECT cached reads:   682 MB in  2.00 seconds = 340.95 MB/sec
 Timing O_DIRECT disk reads: 386 MB in  3.00 seconds = 128.49 MB/sec


sollte eigentlich alles passen.


ich habe auch bereits gegoogelt und gefunden dass die " socket options" auskommentieren soll. Das hat leider auch nichts gebracht.

Samba neu zu installieren hat ebenfalls nichts gebracht.

Firewall ist keine aktiviert.

Wenn ich den Samba Server über Webmin neustarten will bekomme ich ebenfalls einen komischen fehler...

Code:
Fehlgeschlagen den Samba-Server neuzustarten : /etc/init.d/samba start || (/etc/init.d/nmbd start ; /etc/init.d/smbd start) fehlgeschlagen

Ich füge ebenfalls mal meine smb.conf bei


Code:
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic 
# errors. 
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
;   name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
#   security = user

# You may wish to use password encryption.  See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
   encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
;   domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
#   load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
;   printing = bsd
;   printcap name = /etc/printcap

# CUPS printing.  See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
;   printing = cups
;   printcap name = cups

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
#         SO_RCVBUF=8192 SO_SNDBUF=8192
#   ;socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
#   domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
;   winbind enum groups = yes
;   winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each 
# user's home director as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# The following parameter makes sure that only "username" can connect
#
# This might need tweaking when using external authentication schemes
;   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700








[Filme 1]
	valid users = markus
	write list = markus
	path = /shares/HDA_DATA/Filme1

[Filme 2]
	valid users = markus
	path = /shares/HDB_DATA/Filme2
	write list = markus


[Roms]
	valid users = markus
	path = /shares/HDE_DATA/Roms
	write list = markus

[Games]
	valid users = markus
	path = /shares/HDE_DATA/Games
	write list = markus

[Musik]
	valid users = markus
	path = /shares/HDE_DATA/Musik
	write list = markus

[Bilder]
	valid users = markus
	path = /shares/HDE_DATA/Bilder
	write list = markus

[Programme]
	valid users = markus
	path = /shares/HDD_DATA/Programme
	write list = markus

[Johannes]
	valid users = markus
	write list = markus
	path = /shares/HDD_DATA/Johannes

[Stefan Backup]
	valid users = markus
	path = /shares/HDD_DATA/Stefan
	write list = markus

[Public]
	valid users = markus
	path = /shares/HDD_DATA/Public
	write list = markus

[Private]
	valid users = markus
	path = /shares/HDD_DATA/Private
	write list = markus

[Animes]
	valid users = markus
	path = /shares/HDF_DATA/Animes
	write list = markus

[eBooks]
	valid users = markus
	path = /shares/HDD_DATA/eBooks
	write list = markus

[Serien]
	valid users = markus
	path = /shares/HDF_DATA/Serien
	write list = markus

[Workstations]
	valid users = markus
	path = /shares/HDD_DATA/Workstations
	write list = markus

[Filme 3]
	valid users = markus
	path = /shares/HDC_DATA/Filme3
	write list = markus

[Betriebssysteme]
	valid users = markus
	path = /shares/HDD_DATA/Betriebssysteme
	write list = markus

[USBDisk1]
	valid users = markus
	path = /shares/USBDisk1
	write list = markus

[Downloads]
	valid users = markus
	path = /shares/HDD_DATA/Downloads
	write list = markus

[USBDisk2]
	valid users = markus
	path = /shares/USBDisk2
	write list = markus

[USBDisk3]
	valid users = markus
	path = /shares/USBDisk3
	write list = markus

[Webserver]
	valid users = markus
	write list = markus
	path = /var/www

Hat jemand eine Idee oder ähnliche Probleme?


Grüße

Edit:// Über einen FTP Zugang erreiche ich leider nur ähnliche Datenraten
 
Zuletzt bearbeitet:
Ich habe vorhin wegen einem anderen Problem mit Samba gegoogelt und irgendwann in etwa sowas gelesen: Bei Problemen mit langsamer Zugriffsgeschwindigkeit von Windows-Clients aus....blahblah Compression deaktivieren.

Ich versuche mich etwas genauer zu erinnern :)

Edit:

Ah da:

http://wiki.ubuntuusers.de/Samba_Server

"Probleme mit Windows
Falls unter Windows die Performance deutlich zu langsam ist (hauptsächlich Windows 7), hilft unter Umständen eine Abschaltung der "Remote Differential Compression" in der Systemsteuerung von Windows."



....ok, scheint unwahrscheinlich.
 
Zuletzt bearbeitet:
Das hilft leider nichts... unter linux mit samba ändert sich ebenfalls nicht.
FTP läuft auch auf beiden systemen schlecht. muss wohl wirklich direkt mit dem samba server zu tun haben auf dem ubuntu server.
 
Teste bitte mit iperf zwischen den Rechnern, um das Problem aufs Netzwerk einzugrenzen. ifconfig und "netstat -s" output wäre auch nicht schlecht.
 
über iperf: (hoffe ich habe es richtig gemacht, benutze es zum ersten mal)

WLAN -> unten über gbit lan!


Code:
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[  4] local 192.168.1.3 port 5001 connected with 192.168.1.20 port 54968
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-10.1 sec  37.5 MBytes  31.3 Mbits/sec

Ifconfig:

Code:
lo        Link encap:Lokale Schleife
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
          UP LOOPBACK RUNNING  MTU:65536  Metrik:1
          RX-Pakete:20946 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:20946 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:0
          RX-Bytes:6089011 (6.0 MB)  TX-Bytes:6089011 (6.0 MB)

p19p1     Link encap:Ethernet  Hardware Adresse bc:5f:f4:cc:f0:cf
          inet Adresse:192.168.1.3  Bcast:192.168.1.255  Maske:255.255.255.0
          inet6-Adresse: fe80::be5f:f4ff:fecc:f0cf/64 Gültigkeitsbereich:Verbindung
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
          RX-Pakete:3809687 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:8127795 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:1000
          RX-Bytes:3216722985 (3.2 GB)  TX-Bytes:10585578097 (10.5 GB)

ppp0      Link encap:Punkt-zu-Punkt-Verbindung
          inet Adresse:10.3.51.23  P-z-P:10.255.255.255  Maske:255.255.255.255
          UP PUNKTZUPUNKT RUNNING NOARP MULTICAST  MTU:1388  Metrik:1
          RX-Pakete:2248 Fehler:0 Verloren:0 Überläufe:0 Fenster:0
          TX-Pakete:4426 Fehler:0 Verloren:0 Überläufe:0 Träger:0
          Kollisionen:0 Sendewarteschlangenlänge:3
          RX-Bytes:1539229 (1.5 MB)  TX-Bytes:821888 (821.8 KB)

netstat -s

Code:
Ip:
    3822124 Pakete insgesamt empfangen
    0 weitergeleitet
    0 eingehende Pakete verworfen
    3818046 eingehende Pakete ausgeliefert
    8163839 Anforderung gesendet
    4 ausgehende Pakete verworfen
Icmp:
    1135 ICMP-Meldungen empfangen
    10 Input-ICMP-Meldung fehlgeschlagen.
    ICMP-Eingabehistogramm:
        Ziel unerreichbar: 1135
    1133 ICMP Nachrichten gesendet
    0 ICMP Nachrichten fehlgeschlagen
    ICMP-Ausgabehistogramm:
        Ziel unerreichbar: 1133
IcmpMsg:
        InType3: 1135
        OutType3: 1133
Tcp:
    790 aktive Verbindungsöffnungen
    2078 passive Verbindungsöffnungen
    29 fehlerhafte Verbindungsversuche
    52 Verbindungsrücksetzungen empfangen
    12 Verbindungen aufgebaut
    3784029 Segmente empfangen
    8125135 Segmente ausgesendet
    2633 Segmente erneut übertragen
    0 fehlerhafte Segmente empfangen.
    123 Rücknahmen gesendet
Udp:
    50476 Pakete empfangen
    8 Pakete an unbekannten Port empfangen
    0 Paketempfangfehler
    28720 Pakete gesendet
UdpLite:
TcpExt:
    1 ungültige SYN Cookies emfangen
    3 Rücknahmen empfangen für nicht ausgereifte SYN_RECV Sockets
    9 ICMP-Pakete verloren da sie außerhalb des zulässigen Bereichs lagen
    2173 TCP-Sockets haben das Ende der Wartezeit des schnellen Zeitmessers erreicht
    490 verzögerte Acks gesendet
    10 verzögerte Acks aufgrund eines gesperrten Sockets weiter verzögert
    Schneller Ack-Modus wurde 30 mal aktiviert
    82423 Pakete direkt in die recvmsg-Vorwarteschlange eingereiht.
    61775991 bytes directly in process context from backlog
    944629627 bytes directly received in process context from prequeue
    1504585 Paketköpfe prognostiziert
    675127 Paket-Kopfzeilen geschätzt und direkt in die Warteschlange des Benutzers eingereiht
    370284 acknowledgments not containing data payload received
    1171948 vorhergesagte Bestätigungen
    416 times recovered from packet loss by selective acknowledgements
    1 Neuanordnungen über den Zeitstempel erkannt
    1 Überlastungsfenster mit Hoe-Heuristik teilweise wiederhergestellt
    8 congestion windows recovered without slow start by DSACK
    24 congestion windows recovered without slow start after partial ack
    1 Zeitüberschreitungen im Verlustzustand
    1346 Pakete schnell neu versendet
    62 weitergeleitete Wiederholungsübertragungen
    70 andere TCP-Zeitüberschreitungen
    TCPLossProbes: 19165
    TCPLossProbeRecovery: 515
    1 SACK retransmits failed
    30 DSACKs für alte Pakete verschickt
    657 DSACKs empfangen
    8 Verbindungen wegen unerwarteter Daten zurückgesetzt
    1 Verbindungen aufgrund vorzeitigem Abbruch durch den Benutzer zurückgesetzt
    9 Verbindungen infolge Zeitüberschreitung abgebrochen
    TCPDSACKIgnoredNoUndo: 185
    TCPSpuriousRTOs: 21
    TCPSackShiftFallback: 7518
    TCPDeferAcceptDrop: 3
    TCPRetransFail: 5
    TCPRcvCoalesce: 1233150
    TCPOFOQueue: 6068
    TCPSpuriousRtxHostQueues: 166
IpExt:
    InNoRoutes: 2
    InMcastPkts: 13565
    OutMcastPkts: 11661
    InBcastPkts: 1737
    OutBcastPkts: 391
    InOctets: -1122300033
    OutOctets: 1896438618
    InMcastOctets: 2254430
    OutMcastOctets: 1694291
    InBcastOctets: 248032
    OutBcastOctets: 77458


EDIT://

iperf neu mit lan kabel über 1gbit leitung (vorher wlan)


Code:
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 85.3 KByte (default)
------------------------------------------------------------
[  4] local 192.168.1.3 port 5001 connected with 192.168.1.131 port 59941
[ ID] Interval       Transfer     Bandwidth
[  4]  0.0-10.0 sec   143 MBytes   119 Mbits/sec
 
Zuletzt bearbeitet:
hat niemand ne idee?
 
Da das Problem der Download vom Server auf die Clients ist, musst die mit iperf auch diese Richtung testen.
Den server mode (iperf -s) musst du also auf den samba clients starten, und den client mode auf dem Samba server.

Alternative kannst du den bidirektionalen Modus benutzen (-r).


Wenn du ein Ergebnis hier postests, gib bitte immer wo das was und wie gestartet hast, da die iperf Ergebnisse alleine komplett sinnlos sind wenn man den Kontext nicht versteht.
 
Falls es nicht am Netzwerk liegt (bzw. generell mal ne Idee):

Starte mal nen Download und schmeiß iotop an, da siehst du vielleicht, wo / wieso es klemmt...
 
Zurück
Oben