1834480 Members
3152 Online
110067 Solutions
New Discussion

Re: samba lock error

 
Darren Gibbs
Advisor

samba lock error

We are having a locks issue since upgrading one of our servers to HPUX 11.11 and installing CIFS 1.08. The log.nmbd has entries as follows:

[2002/11/25 11:45:37, 0] tdb/tdbutil.c:(475)
tdb(/var/opt/samba/locks/unexpected.tdb): tdb_lock failed on list -1 ltype=2 (No locks available)
[2002/11/25 11:49:19, 0] tdb/tdbutil.c:(475)
tdb(/var/opt/samba/locks/unexpected.tdb): tdb_lock failed on list -1 ltype=2 (No locks available)
[2002/11/25 12:03:40, 0] tdb/tdbutil.c:(475)
tdb(/var/opt/samba/locks/unexpected.tdb): tdb_lock failed on list -1 ltype=2 (No locks available)
[2002/11/25 12:03:40, 0] tdb/tdbutil.c:(475)

Any ideas?
4 REPLIES 4
Ken Hubnik_2
Honored Contributor

Re: samba lock error

I would check the permissions on /var/opt/samba/locks and make sure the the master samba user can read/write to the directory.
Darren Gibbs
Advisor

Re: samba lock error

The permissions are 750 on the /var/opt/samba/locks directory. I did notice a lot of *.tdb files with this new version. Examples are messages.tdb, printing.tdb, share_info.tdb, etc. The permissions on those are all 600.
Ken Hubnik_2
Honored Contributor

Re: samba lock error

Stefan Pendl
Valued Contributor

Re: samba lock error

Hi Darren,
this is definitly a problem with the nflocks kernel parameter.
for release A.01.08 upwards you will have to increase the nfiles and nflocks parameters as described in the release notes (find them attached).
since the maxusers parameter controls the value of nfiles, i use the formula (10*maxusers) for nflocks.
I recommend upgrading to release A.01.08.01 of CIFS 9000/Server there are big problems with A.01.08.

---
steve
Programing is fun.