Thanks Volker, I've Changed the values as you suggested, i noticed that the default value for max xmit is much less 16384! Still I feel like the performance is very slow indeed. This because on server, a can make copys arround 8gb/s! and in samba is all so slow and it freezes as i sad many times...

Can you have a second look to the log, to see if you see anything strange? I'm putting a dump off the level 1 log, for you to check, i know it's more general, but if you notice anything, then i will increase it to see it better!

[2012/01/04 11:07:44.992938, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/01/04 11:08:04.996512, 1] smbd/server.c:266(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2012/01/04 11:08:41.711133, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/01/04 11:09:01.717859, 1] smbd/server.c:266(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2012/01/04 12:01:53.685263, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/01/04 12:02:13.689221, 1] smbd/server.c:266(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2012/01/04 12:07:36.437089, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/01/04 12:07:56.441751, 1] smbd/server.c:266(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2012/01/04 12:17:37.812975, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/01/04 12:17:57.816510, 1] smbd/server.c:266(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2012/01/04 13:02:45.073818, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/01/04 13:03:05.085521, 1] smbd/server.c:266(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2012/01/04 13:07:18.905277, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/01/04 13:07:38.906269, 1] smbd/server.c:266(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2012/01/04 13:14:37.957566, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/01/04 13:14:57.958360, 1] smbd/server.c:266(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2012/01/04 13:17:40.097021, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/01/04 13:18:00.100073, 1] smbd/server.c:266(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2012/01/04 14:02:39.801610, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/01/04 14:02:59.812268, 1] smbd/server.c:266(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2012/01/04 14:03:18.601017, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/01/04 14:03:38.603099, 1] smbd/server.c:266(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2012/01/04 14:11:43.877235, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/01/04 14:12:03.879569, 1] smbd/server.c:266(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2012/01/04 15:07:39.429117, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/01/04 15:07:59.429898, 1] smbd/server.c:266(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown [2012/01/04 15:15:44.592951, 1] smbd/server.c:294(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2012/01/04 15:16:04.596144, 1] smbd/server.c:266(cleanup_timeout_fn) Cleaning up brl and lock database after unclean shutdown Many Thanks! Vasco Leal Best Regards, Vasco Leónidas Pinto Leal IT Director JUZO - Informática e Serviços, Lda Mozilla Thunderbird, The Mail Rebirth! Still Stucked With Windows? Give Linux a Try And Enhance Your Work! Em 04-01-2012 08:57, Volker Lendecke escreveu: > On Tue, Jan 03, 2012 at 11:26:06PM +0000, Vasco Leal wrote: >> When accessing the shares on my samba server, it sometimes freezes, >> i have the lateste version, 3.6.1, mas since version 3.4 wish was >> the first i used, i've been running into this problems. When i try >> to browse the shares, many times, like 1 in 10, it freezes and >> sometimes, when saving files, it fails at the first command and only >> at the second command to save it does so. >> >> My other problem is with samba very low performance, i have 50 >> computers on the office, have 1000mbps connections, 3 1000mbps ports >> being used just for samba as a bond, and still the performance is >> very low, my server is a hp dl380 g6 with 24GB of memory, dual xeon >> at 2.4Ghz and 2 Sas controllers with 1024MB memory each, so i >> shouldn't be experiencing any delay. I'll Put a dump of both my >> smb.conf and smbd.log. >> >> Hope to get Some Help cause this is driving me crazy!!! >> >> *smb.conf* >> >> #Date: 2011/02/19 00:34:22 >> >> [global] >> >> security = user >> >> workgroup = NLAdomain >> >> netbios aliases = NLSRV >> >> server string = NLSRV >> >> name resolve order = wins host bcast >> >> socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE >> SO_RCVBUF=65536 SO_SNDBUF=65536 > Please remove the SO_RCVBUF and SO_SNDBUF options. > >> log level = 4 > For maximum performance, log level = 1 is sufficient, > although 4 should not affect it badly yet. > >> max log size = 50 > This is very, very small. > >> max xmit = 65535 > Please remove this parameter. > > If transfers are still slow or stall, I would investigate > the hardware you are using. It can be anything from bad > network cables to flaky disks, something which is difficult > to judge without direct machine access. Trying transfer via > ftp might give you hints. > > With best regards, > > Volker Lendecke >
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

Reply via email to