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

[Alex Crow]

On 03/11/16 08:51, Martin Schwenke via samba wrote:
> On Thu, 3 Nov 2016 08:13:53 +0100, Ralph Böhme via samba
> <samba at lists.samba.org> wrote:
>
>> On Thu, Nov 03, 2016 at 05:34:21PM +1100, Martin Schwenke via samba wrote:
>>> 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?
> Sure.  I was glossing over a lot of details... but I hope we would
> notice major breakage like that...  :-)
>
>>> 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.
> Yay!
>
> peace & happiness,
> martin
>

This is very strange. I've tested with 3 separate clusters and can 
replicate the problem every time if a 3rd node is in the picture.

The filesystem could not be an issue could it? It passes ping_pong just 
fine.

Cheers

Alex
--
This message is intended only for the addressee and may contain
confidential information. Unless you are that person, you may not
disclose its contents or use it in any way and are requested to delete
the message along with any attachments and notify us immediately.
This email is not intended to, nor should it be taken to, constitute advice.
The information provided is correct to our knowledge & belief and must not
be used as a substitute for obtaining tax, regulatory, investment, legal or
any other appropriate advice.

"Transact" is operated by Integrated Financial Arrangements Ltd.
29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300.
(Registered office: as above; Registered in England and Wales under
number: 3727592). Authorised and regulated by the Financial Conduct
Authority (entered on the Financial Services Register; no. 190856).