[Samba] CTDB and locking issues in 4.4.6 (Classic domain)

[Ralph Böhme]

Hi Martin,

On Thu, Nov 03, 2016 at 05:34:21PM +1100, Martin Schwenke via samba wrote:
> On Wed, 2 Nov 2016 11:29:13 +0000, Alex Crow via samba
> <samba at lists.samba.org> wrote:
> 
> > On 02/11/16 07:29, Ralph Böhme wrote:
> > 
> > > On Tue, Nov 01, 2016 at 09:56:06PM +0000, Alex Crow wrote:  
> >  [...]  
> > >> Hi Ralph,
> > >>
> > >> Thanks for that. Can I post the above back to the ML with links to
> > >> appropriate logs?  
> > > sure.
> > >
> > > Btw, I forgot to mention that I did test this on my own devel cluster,
> > > both development version from git master as well as production 4.4,
> > > and could not reproduce the issue.
> > >
> > > -slow  
> > 
> > Is anyone able to assist with this issue? I have produced level 10 logs 
> > but not sure how to debug CTDB.
> 
> If you lock the file from a client attached to 1 node and
> "smbstatus -L" shows the lock from all the nodes then CTDB is doing
> what it is meant to.  That is, it makes sure that Samba processes see
> the same TDB records on all nodes.

hm, smbstatus does a db traverse while smbclient will trigger a
migrate record, so both use different ctdb protcol ops, don't they?

> Not sure what's going on with the rest of it.  Doing a bit of testing...

I tested on a 3 node test cluster, with 4.4.x and master, works as
expected.

-slow