We are using SAMBA 2.2.3a on HPUX 11.0 and are running into a problem where after 30 sessions, noone else can access the shares. We have eight 60 GB read-only shares. Our test consists of a batch file that checks 64 times for the command file on one of the shares. We get around 30 sessions running and everything after that fails to find the command file. Are there limits in SAMBA on sessions/shares/locks ??? Is there something in HPUX that would limit samba sessions? Guidance and counsel, please! Paul Orwig Pacific Life
I am not sure, but most Unix and Linux system has a file descriptor and number of processes allowed. The file descriptors are important because I believe each open file or tcp/ip connection requires a file descriptor. The file descriptors are limited both on a global basis and a per process basis. An example is ulimit -a will show some of the limitiation associated with an open session. Note, this may not be applicable to the process that started to the smb especially the file descriptor limitiation. The global process limitiation may limit you. The process limit is important because it limits the number of processes a single process can start. You might want to check out your system and see what your file descriptor and process limitiation and see if your machine is exceeding the global limits. Orwig, Paul wrote:>We are using SAMBA 2.2.3a on HPUX 11.0 and are running into a problem where >after 30 sessions, noone else can access the shares. > >We have eight 60 GB read-only shares. > >Our test consists of a batch file that checks 64 times for the command file >on one of the shares. We get around 30 sessions running and everything after >that fails to find the command file. > >Are there limits in SAMBA on sessions/shares/locks ??? > >Is there something in HPUX that would limit samba sessions? > >Guidance and counsel, please! > >Paul Orwig >Pacific Life >-- Joseph Loo jloo@acm.org
Paul,
I'm not sure if this is true for read only shares. But we have run into
similar problems due to the kernel parameter nfile (number of available
filelocks) which defaults to 200 on HP-UX. In our case this limits the number
of users to about 20. Samba
complains loudly about this situation: it has no locks available to open
it's .tdb. Please check for such messages in your logs.
You can safely increase (reboot required of course) this to, say, 5000. It takes
about 100 /120 bytes of system memory per configured filelock. You may also want
to check the usage of this parameter with glance or gpm before you make any
changes
-
Regards,
Reinout Wijnveen
"All those who believe in psychokinesis raise my hand"
ICT-N/Philips Semiconductors Nijmegen
Address: AC 0.061, Gerstweg 2, 6534 AE Nijmegen
Fax: +31 24 353 2019
Tel. +31 24 353 3631
Joseph Loo
<jloo@acm.org> To: samba list
<samba@lists.samba.org>
Sent by: cc: (bcc: Reinout
Wijnveen/NYM/SC/PHILIPS)
samba-admin@list Subject: Re: [Samba] Samba
limits on HPUX???
s.samba.org
Classification:
03/20/02 03:30
PM
I am not sure, but most Unix and Linux system has a file descriptor and
number of processes allowed. The file descriptors are important because
I believe each open file or tcp/ip connection requires a file
descriptor. The file descriptors are limited both on a global basis and
a per process basis. An example is ulimit -a will show some of the
limitiation associated with an open session. Note, this may not be
applicable to the process that started to the smb especially the file
descriptor
limitiation. The global process limitiation may limit you. The process
limit is important because it limits the number of processes a single
process can start.
You might want to check out your system and see what your file
descriptor and process limitiation and see if your machine is exceeding
the global limits.
Orwig, Paul wrote:
>We are using SAMBA 2.2.3a on HPUX 11.0 and are running into a problem where
>after 30 sessions, noone else can access the shares.
>
>We have eight 60 GB read-only shares.
>
>Our test consists of a batch file that checks 64 times for the command file
>on one of the shares. We get around 30 sessions running and everything after
>that fails to find the command file.
>
>Are there limits in SAMBA on sessions/shares/locks ???
>
>Is there something in HPUX that would limit samba sessions?
>
>Guidance and counsel, please!
>
>Paul Orwig
>Pacific Life
>
--
Joseph Loo
jloo@acm.org
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
Thank you, Reinout and Eric.
The nflocks kernal parameter looks to have made the difference.
We will be doing a larger stress test tomorrow (Friday)
Thanks again!
Paul Orwig
Pacific Life
<Original Message>
From: reinout.wijnveen@philips.com
Subject: Re: FW: [Fwd: Re: [Samba] Samba limits on HPUX???]
To: "ROSEME,ERIC H (HP-Roseville,ex1)" <eric_roseme@hp.com>
Cc: samba@lists.samba.org
Date: Thu, 21 Mar 2002 16:45:27 +0100
Oops, yes: it should defintely be nflocks. Thanks and sorry to all others
Maybe 7:45 was a bit too early to think clear ;-)
I don't have the e-mail adres of the original poster handy so i'll copy
the
samba list.
-
Regards,
Reinout Wijnveen
"All those who believe in psychokinesis raise my hand"
ICT-N/Philips Semiconductors Nijmegen
Address: AC 0.061, Gerstweg 2, 6534 AE Nijmegen
Fax: +31 24 353 2019
Tel. +31 24 353 3631
"ROSEME,ERIC H
(HP-Roseville,ex To: Reinout
Wijnveen/NYM/SC/PHILIPS@EMEA2
1)" cc:
<eric_roseme@hp. Subject: FW: [Fwd: Re:
[Samba] Samba limits
com> on HPUX???]
03/21/02 04:29 Classification:
PM
Hi Reinout,
Did you mean nflocks? I've attached the 11i kernel tuning guide for
reference - pages 29 and 33.
Sorry if I've got this wrong.
Eric Roseme
Technical Consultant
Systems Networking Solutions Lab ATC
Hewlett-Packard
eric_roseme@hp.com
-----Original Message-----
From: Eric Roseme [mailto:eroseme@emonster.rose.hp.com]
Sent: Thursday, March 21, 2002 7:20 AM
To: eric roseme
Subject: [Fwd: Re: [Samba] Samba limits on HPUX???]
-------- Original Message --------
Subject: Re: [Samba] Samba limits on HPUX???
Date: Thu, 21 Mar 2002 08:07:04 +0100
From: reinout.wijnveen@philips.com
To: samba list <samba@lists.samba.org>
CC: samba-admin@lists.samba.org
Paul,
I'm not sure if this is true for read only shares. But we have run into
similar problems due to the kernel parameter nfile (number of available
filelocks) which defaults to 200 on HP-UX. In our case this limits the
number of users to about 20. Samba
complains loudly about this situation: it has no locks available to open
it's .tdb. Please check for such messages in your logs.
You can safely increase (reboot required of course) this to, say, 5000.
It takes about 100 /120 bytes of system memory per configured filelock.
You may also want to check the usage of this parameter with glance or
gpm before you make any changes
-
Regards,
Reinout Wijnveen
"All those who believe in psychokinesis raise my hand"
ICT-N/Philips Semiconductors Nijmegen
Address: AC 0.061, Gerstweg 2, 6534 AE Nijmegen
Fax: +31 24 353 2019
Tel. +31 24 353 3631