Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 21/06/2007, à 17:32

darkgate

Samba terriblement lent en récéption.

Bonjour à tous,

N'ayant pas trouvé de réponse concluante ni sur ce Forum ni sur d'autre je viens à vous pour demander de l'aide.

Matériel:
Serveur: Ubuntu Server Feisty, Carte Eth0 Intel pro 100 et carte eth1 Realteak 8169 1Gbt/s.
Poste client: Windowze XP SP2 à jour avec carte Nvidia et Marvell à 1Gbt/s.

Le problème:
Quand j'envoi des fichiers sur le serveur par Samba c'est lent à mourir, environ 10Mbts/s.
par contre en réception ça monte à environ 330Mbts/s
J'ai donc essayé d'envoyer un gros fichier par FTP et la ça monte 420Mbts/s par seconde.
Donc je suppose que ça ne viens pas de mon matériel mais de samba qui gère très mal la réception.

Que puis je contrôler ou modifier pour remédier à ce problème ???

Merci d'avance pour vos réponses.

Dernière modification par darkgate (Le 21/06/2007, à 19:09)

Hors ligne

#2 Le 21/06/2007, à 19:07

darkgate

Re : Samba terriblement lent en récéption.

Pour info:

J'ai tout de même essayé de mettre le module du fabricant de ma carte réseau Realteak avec laquelle je fais mes transferts entre mon poste windows et mon serveur Ubuntu. Que ce soit avec le module d'origine ou celui du fabricant le résultat est le même:
en passant par FTP: dans les 2 sens très bon transfert ~42Mo/s.
en passant par Samba: Ubuntu --> Windows  ~35Mo/s mais de Windows --> Ubuntu  ~1Mo/s.

Je ne sais plus quoi faire.
D'ou vient le problème???

Merci de m'aider SVP.

Hors ligne

#3 Le 21/06/2007, à 19:22

darkgate

Re : Samba terriblement lent en récéption.

Encore un autre test:

J'ai tester les mêmes transferts avec NFS (j'ai installé le client NFS sur windows) et les résultats sont les mêmes à peu près que Samba:
Ubuntu --> Windows  ~35Mo/s mais de Windows --> Ubuntu  ~1Mo/s.

Voila ! Si vous voulez que je fasse d'autres tests je suis ouvert à toutes idées...

Hors ligne

#4 Le 22/06/2007, à 08:31

darkgate

Re : Samba terriblement lent en récéption.

UP smile

Personne pour m'aider ???

Hors ligne

#5 Le 29/06/2007, à 08:56

darkgate

Re : Samba terriblement lent en récéption.

Up!

Hors ligne

#6 Le 30/06/2007, à 14:28

Charckut

Re : Samba terriblement lent en récéption.

J'ai le même problème que toi, un débit faible avec samba et nfs je n'ai pas réussi à le faire fonctionner!:/
Si quelqu'un a une explication pour samba? smile

Dernière modification par Charckut (Le 30/06/2007, à 20:24)

Hors ligne

#7 Le 30/06/2007, à 16:21

Caes

Re : Samba terriblement lent en récéption.

Copie le smb.conf. Que donne un testparm de ce fichier ?
Comme ça, je ne vois pas trop le problème, mais cela peut peut être provenir si tu fais un broadcast sur le réseau (si ton smb.conf utilise le broadcast au lieu d'un wins ou d'un dns,...).

Après vérifie bien sûr tes pare-feu linux/windows... je ne pense pas que le problème provienne du système de fichiers différents (par exemple ext3, ntfs,etc,...).

Sinon tu peux mettre en place sur ton linux Netatalk pour voir les diffs.

Dernière modification par Caes (Le 30/06/2007, à 16:22)

Hors ligne

#8 Le 03/07/2007, à 01:00

darkgate

Re : Samba terriblement lent en récéption.

Voici mon smb.conf

Si quelqu'un voit une quelquonque anomalie

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

[global]

## Browsing/Identification ###

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

# 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 = yes

# 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 = yes

# 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 = true
disable netbios = yes


#### Debugging/Accounting ####

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

# Put a capping on the size of the log files (in Kb).
   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

;   guest account = nobody
   invalid users = root

# 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\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\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 = no

########## 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
;   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

########## 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

# When using [print$], root is implicitly a 'printer admin', but you can
# also give this right to other users to add drivers and set printer
# properties
;   printer admin = @lpadmin


############ 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

#======================= 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 directory as \\server\username
[homes]
   comment = Home Directories
   browseable = no

# 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
   valid users = %S

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

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

# 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

Voial ce que me donne testparm:

Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Server role: ROLE_DOMAIN_PDC
Press enter to see a dump of your service definitions

[global]
        workgroup = MORDOR
        server string = %h server (Samba, Ubuntu)
        obey pam restrictions = Yes
        passdb backend = tdbsam
        passwd program = /usr/bin/passwd %u
        passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .
        unix password sync = Yes
        syslog = 0
        log file = /var/log/samba/log.%m
        max log size = 1000
        disable netbios = Yes
        name resolve order = lmhosts host wins bcast
        domain logons = Yes
        wins support = Yes
        panic action = /usr/share/samba/panic-action %d
        invalid users = root

Merci pour vos réponses

Dernière modification par darkgate (Le 03/07/2007, à 01:01)

Hors ligne