[Samba] Eclipse (Java) locking issues after upgrade (3.6.23 -> 4.4.3)

[Luc Lalonde]

Hello Jeremy,

Could you send me some references to the ‘cross-protocol issue’ (Bugzilla, documentation, etc)?

I’ll disable the ‘kernel oplocks’ and see what happens.

We’re getting all sorts of weirdness from our Mac SMB clients since we upgraded to Samba v4.4.3.

In particular, when we open a session with an OSX (Yosemite) client with SMB autommount directories, we see multiple SMBD processes that take up almost 100% of the Samba server’s processes.

I have to kill all of the SMBD processes on the server and reboot the client to get out of this situation!  

If I can’t resolve this before classes begin in September, I’ll have to go back to using AFP (Netatalk) for our Mac labs.

My Windows 8.1 and Windows 10 clients work fine and do not cause this problem. 

Best regards, Luc.

> On May 27, 2016, at 7:15 PM, Jeremy Allison <jra at samba.org> wrote:
> 
> On Tue, May 24, 2016 at 12:41:32PM -0400, Luc Lalonde wrote:
>> Hello Jeremy,
>> 
>> Sorry for the long delay for responding to your request (just came
>> back to the office after long Victoria day weekend).
>> 
>> I'm not sure if it's Ok to send such large attachements to the list.
>> So here's a Dropbox public link to download it:
>> 
>> https://www.dropbox.com/s/o2617jtqfbwlyhc/eclipse-java-samba-level10.log.gz?dl=0
>> 
>> All our connections to this share are not all via Samba.   We use it
>> for Linux diskless (via kernel, Pam_Mount) and Windows clients.
>> 
>> That's why we use 'kernel oplocks = yes'.  Maybe we don't need it?
>> Could it be the source of our problem?
>> 
>> Please don't hesitate to get in touch if you need more info...
> 
> Start by removing all access other than Samba, and see if
> you can still reproduce the problem. If not, then it's
> the cross-protocol issue.
> 
> If you can still reproduce with only SMB clients, ping
> me again :-).
> 
> Cheers,
> 
> 	Jeremy.