Hi,
I bet they are but I see thousands of them per second for every client
that is 'just connected' and not doing anything, (on solaris) it slows
down a t5120 machine with five connections to become unusable... I see the
problem with:
samba-3.0.20
samba-3.2.14
samba-3.3.10
samba-3.4.1
samba-3.4.5
stopped trying more versions than as there was no single response on this
list and changed my service to a linux box where all of these versions run
just fine :)
cheers
christoph
On Thu, 1 Apr 2010, Volker Lendecke wrote:
On Thu, Apr 01, 2010 at 01:32:02PM +0200, Christoph Beyer wrote:
if you do 'truss -f -p <smbd-PID>' do you see a lot of:
19702: fcntl(17, F_SETLKW64, 0xFFBFE640) = 0
?
If yes this is a problem that is present in most of the recent samba
versions (tried 5 or 6 versions off the different branches) it's a
solaris related bug but that's all I can say. It might be fixed in 3.5.1
...
Those many fcntl calls are just normal Samba operation. They
should be *very* fast. There might be a problem with the
messages.tdb, notify.tdb and notify_onelevel.tdb in current
Samba version, where there is one fcntl read lock being held
per smbd on each of these databases. This might be a
performance problem if you have thousands of connected
clients. But normally, fcntl calls should be very fast.
Volker
best regards
~christoph
--
/* Christoph Beyer | Office: Building 2b / 23 *\
* DESY | Phone: 040-8998-2317 *
* - IT - | Fax: 040-8998-4060 *
\* 22603 Hamburg | http://www.desy.de */
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
