[Samba] release_posix_lock: unable to find entry to delete with Samba3.0.23b on Redhat ES4

[Andrew Wilson]

Hello Jeremy,

Thanks for the response. I forgot to add in my original posting that we 
did not see this problem with Samba3.0.22 on the same system with the 
same smb.conf file.

I notice that in the smb.log file, these errors always occur in pairs - 
having exactly the same time, date and content. There is usually a few 
minutes between their occurance - sometimes as much as half an hour. I 
know this probably isn't much help, but I notice that the errors stop 
outside working hours - suggesting (to me) that they are occuring in 
response to our users initiating some file/print action on their PC's. 
This at least gives me a hint to investigate how to replicate the problem.

Unfortunately I am out of the office for the next week - I will get my 
colleauges to gather some more information on the problem and try to 
find a way to replicate the errors. Will post again when I have any 
further information.

Many thanks for your help

Andrew

Jeremy Allison wrote:

>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.
>
>________________________________________________________________________
>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
>________________________________________________________________________
>  
>


________________________________________________________________________
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
________________________________________________________________________