Locking, notify collisions using CTDB on non-clustered share?

[Christopher R. Hertel]

I double checked the errors I was getting just to be sure.  Some of the ones
I reported are bogus (as in, they occur on stand-alone systems as well as
matching non-clustered shares within a cluster and so are not of interest).
In the list below, there are two that can be ignored:

Ignore: (../source4/torture/smb2/notify.c:118) Incorrect status
NT_STATUS_INVALID_PARAMETER - should be NT_STATUS_OK

Ignore: (../source4/torture/smb2/notify.c:636) wrong value for
notify.smb2.out.num_changes  0xb should be 0x9

The above two are "normal".  Others in the list below are not "normal", in
that they do not appear the share paths are unique.

> Some more example errors seen when the share paths are the same (3-node
> cluster):
> [172.31.47.126] (../source4/torture/smb2/notify.c:118) Incorrect status NT_STATUS_INVALID_PARAMETER - should be NT_STATUS_OK
> [172.31.47.126] (../source4/torture/smb2/notify.c:324) wrong value for notify.smb2.out.num_changes  0xa should be 0x4
> [172.31.47.126] (../source4/torture/smb2/notify.c:636) wrong value for notify.smb2.out.num_changes  0xb should be 0x9
> [172.31.47.194] (../source4/torture/smb2/notify.c:118) Incorrect status NT_STATUS_INVALID_PARAMETER - should be NT_STATUS_OK
> [172.31.47.194] (../source4/torture/smb2/notify.c:394) wrong value for notify.smb2.out.num_changes  0xb should be 0xa
> [172.31.47.194] (../source4/torture/smb2/notify.c:636) wrong value for notify.smb2.out.num_changes  0xe should be 0x9
> [172.31.39.200] (../source4/torture/smb2/notify.c:118) Incorrect status NT_STATUS_INVALID_PARAMETER - should be NT_STATUS_OK
> [172.31.39.200] (../source4/torture/smb2/notify.c:324) wrong value for notify.smb2.out.num_changes  0xa should be 0x4
> [172.31.39.200] (../source4/torture/smb2/notify.c:634) Incorrect status STATUS_NOTIFY_ENUM_DIR - should be NT_STATUS_OK
> 
> Chris -)-----
>