samba - Aug 2006 - release_posix_lock: unable to find entry to delete with Samba3.0.23b on Redhat ES4

We are running Samba3.0.23b on Redhat ES4 and find that we are getting 
quite a few of the release_posix_lock errors appearing in the SAMBA log 
(See base of this note). There is no obvious impact on the operation of 
the system, but I was wondering if anyone else is experiencing the same 
and whether we need to worry about this. We have the default "posix 
locking=yes" in operation and I note in the man entry that we "should 
never need to disable this parameter". However if we do turn it off, the 
errors appear to go away. I suspect though that this means that there is 
not full lock integrity on our files?

We are using exactly the same settings with Samba3.0.23b on both Solaris 
8 and Solaris 10 and we do not see this problem. Our Redhat system is 
fully patched up to date and so is the gcc we are compiling samba with.

See entries from log.smb below.

Andrew

[2006/08/18 08:04:37, 0] lib/util.c:smb_panic(1592)
  PANIC (pid 7536): release_posix_lock: unable find entry to delete !
 
[2006/08/18 08:04:37, 0] lib/util.c:log_stack_trace(1699)
  BACKTRACE: 14 stack frames:
   #0 /opt/samba/sbin/smbd(log_stack_trace+0x1a) [0x552acab33c]
   #1 /opt/samba/sbin/smbd(smb_panic+0x69) [0x552acab1d1]
   #2 /opt/samba/sbin/smbd(release_posix_lock+0x11a) [0x552ac64e11]
   #3 /opt/samba/sbin/smbd [0x552ac60f86]
   #4 /opt/samba/sbin/smbd(brl_unlock+0x46) [0x552ac61a32]
   #5 /opt/samba/sbin/smbd(do_unlock+0x164) [0x552ac5e0b1]
   #6 /opt/samba/sbin/smbd(reply_lockingX+0x57c) [0x552ab4431f]
   #7 /opt/samba/sbin/smbd [0x552ab72a91]
   #8 /opt/samba/sbin/smbd [0x552ab72b51]
   #9 /opt/samba/sbin/smbd [0x552ab72eb4]
   #10 /opt/samba/sbin/smbd(smbd_process+0x140) [0x552ab73caa]
   #11 /opt/samba/sbin/smbd(main+0x894) [0x552ad4045a]
   #12 /lib64/tls/libc.so.6(__libc_start_main+0xdb) [0x2a96b883fb]
   #13 /opt/samba/sbin/smbd [0x552ab078fa]
[2006/08/18 08:04:37, 0] lib/fault.c:dump_core(168)
  unable to change to /opt/samba/var/log.smb/cores/smbdrefusing to dump core



________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

On Fri, Aug 18, 2006 at 08:19:16AM +0100, Andrew Wilson
wrote:
> We are running Samba3.0.23b on Redhat ES4 and find that we are getting 
> quite a few of the release_posix_lock errors appearing in the SAMBA log 
> (See base of this note). There is no obvious impact on the operation of 
> the system, but I was wondering if anyone else is experiencing the same 
> and whether we need to worry about this. We have the default "posix 
> locking=yes" in operation and I note in the man entry that we
"should
> never need to disable this parameter". However if we do turn it off,
the
> errors appear to go away. I suspect though that this means that there is 
> not full lock integrity on our files?
> 
> We are using exactly the same settings with Samba3.0.23b on both Solaris 
> 8 and Solaris 10 and we do not see this problem. Our Redhat system is 
> fully patched up to date and so is the gcc we are compiling samba with.
Strange. You're hitting a deliberate panic due to what smbd believes
is a logic error in the lock counts. Can you find out more about how
you reproduce this problem ? Is there anything specific you're doing
when it happens ?

Jeremy.