samba3 crash

Jeremy Allison jra at samba.org
Tue Jun 5 17:44:24 GMT 2007


On Tue, Jun 05, 2007 at 02:30:30PM +0200, Stefan (metze) Metzmacher wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> >> home/build/build_farm/samba_3_0.metze/source/bin/smbd"
> >>         result = 1696625253
> >> #5  0x374ecc in byte_range_lock_destructor (br_lck=0x40164868) at
> >> locking/brlock.c:1578
> >>         data = {dptr = 0x401b90c8 "", dsize = 8832}
> >>         status = {v = 3221225473}
> >>         key = {dptr = 0x40164878 "", dsize = 16}
> >> #6  0x3c862c in _talloc_free (ptr=0x40164868) at lib/talloc/talloc.c:0
> >> No locals.
> >> #7  0x3c9630 in talloc_free (ptr=0x40164868) at lib/talloc/talloc.c:0
> 
> I just found the difference between LOCK3 and BASE-LOCK-LOCK3
> samba has torture_numops=100 and samba4 has torture_numops=10
> 
> when I change it to 10 in samba3 it also doesn't appear...
> 
> should we change samba4 to 100 again?

Oh, is this on HPUX ? HPUX is one of the insane
systems that has a hard coded limit on the number
of allowable fcntl locks. You have to change a
kernel tunable and reboot to fix this.

If it's running out of fcntl locks on HPUX this
is a known HPUX bug - we tell people to up the
number of allowable locks and reboot.

Jeremy.


More information about the samba-technical mailing list