[Samba] tdb lock failures

[Jeremy Allison]

On Tue, Jun 29, 2004 at 04:34:02PM +0100, David Nash wrote:
> We've just gone live with a file & print server, and are having major
> problems with Samba.  When used out of hours, with all PCs switched on
> and connected to the domain, everything works fine.  However, during the
> day, we have problems where users can't print to any samba-hosted
> printer, Access database applications (where the database is held on the
> server) won't work, or work briefly before experiencing data corruption.
> Our system log file is filling at an alarming rate with messages about
> tdb lock failures.
> 
>   tdb(/usr/lib/samba/var/locks/brlock.tdb): tdb_lock failed on list 39
> ltype=2 (No record locks available)
> [2004/06/29 11:00:45, 0] tdb/tdbutil.c:(531)
>   tdb(/usr/lib/samba/var/locks/brlock.tdb): tdb_lock failed on list 39
> ltype=1 (No record locks available)
> [2004/06/29 11:00:45, 0] tdb/tdbutil.c:(531)
>   tdb(/usr/lib/samba/var/locks/brlock.tdb): tdb_unlock: count is 0
> [2004/06/29 11:00:45, 2] smbd/close.c:(229)
>   janette closed file Wills04/~$25.1will.jrh.doc (numopen=9) 
> [2004/06/29 11:00:48, 0] tdb/tdbutil.c:(531)
>   tdb(/usr/lib/samba/var/locks/locking.tdb): tdb_lock failed on list 65
> ltype=2 (No record locks available)
> 
> We're on UnixWare 7.1.3.Pack 3, and Samba 2.2.8a

It looks like UnixWare has limits on the number of fcntl locks a process
can have. Modern Linux and UNIX systems don't have this. You need to find
a way to increase the number of fcntl locks available to smbd processes,
but I don't know anything about UnixWare.

UnixWare I believe is a SCO product. Are you sure you feel safe using a
product from a company that sues its customers as a business model ?

I would strongly recommend moving to a supported platform such as SuSE
Linux (now owned and supported by Novell) or RedHat, or one of the many
other Linux distributions out there. They don't have fcntl lock limits.

Jeremy.