samba - Oct 2016 - CTDB and locking issues in 4.4.6 (Classic domain)

On Thu, Oct 20, 2016 at 8:09 PM, Alex Crow via samba <samba at
lists.samba.org>
wrote:
> Hi list
>
> We recently upgraded our fileservers from Centos supplied 4.2.10 to Sernet
> 4.4.6, and then our DCs from 3.6.x to 4.4.6.
>
> It seems that since then we've had problems with locks not being obeyed
on
> all nodes - they only seem to work when a second client opens a file on the
> same node as the first client.
>
> For example, when a user opens an Excel file I will see something like
> this with smbstatus -L:
>
> 1:30578      1608       DENY_WRITE 0x2019f     RDWR       NONE /sharename
> path/foo.xls
>
> This output is identical on all nodes, so smbstatus at least can see the
> locks.
>
> However if another client opens the same XLS file, they only get the
"This
> file is in use by <username>" if they happen to hit the same
server as the
> first user. If they happen to land on another server they don't get
this
> prompt, and if the original user modifies the file, when they try to save
> their changes they get prompted whether they want to overwrite. I'm
sure we
> didn't have this issue before the upgrade.
>
> CTDB status reports as OK on all nodes.
>
> Our filesystem passes ping_pong in both read and read/write, data
> increment behaving as expected.
>
> We have a lot of users trying to edit Excel and Word docs (Office 2010) so
> this is happening quite often.
>
> Best regards,
>
> Alex
>
>
It appears that samba is still using local databases and not clustered
databases.

What does "ctdb getdbmap" list?  Is locking.tdb a clustered database? 
Do
you have "clustering = yes" in smb.conf on all the nodes?

Amitay.

Hi Alex,

On Thu, 20 Oct 2016 14:28:38 +0100, Alex Crow via samba
<samba at lists.samba.org> wrote:
> >
> > It appears that samba is still using local databases and not clustered
> > databases.
> >
> > What does "ctdb getdbmap" list?  Is locking.tdb a clustered
database?
> > Do you have "clustering = yes" in smb.conf on all the nodes?
> >
> > Amitay.  
> 
> FYI as stated smbstatus -L shows locks from all hosts, prefixed by the PNN.
That tells you that the locks are correctly stored in CTDB and
smbstatus can find them.  This means that smbd should be able to find
them too.

I can't help but think that smbd is somehow using different
configuration than smbstatus.

You don't have smbd/smbstatus installed from a package in /usr/ and the
other left over in /usr/local/, or similar?  In that case, they could
be getting their configurations from different places...

peace & happiness,
martin