samba - Jun 2019 - Update 4.10.2 to 4.10.4: Cant create files in subdirectorie anymore

You're totally right and after i rechecked my conf i've seen that i
already set
vfs objects = acl_xattr gluster
in my share definition. I just played around with these options to see if it
helps.
Neither combination made any difference so i guess my problem isnt related to
the xattr module,
it could be related to the gluster module since i did'nt check what would
happen if i'd use a local disk
but using a local disk or another clustered FS is no option for me.
I'm not sure but i think i stumbled upon a bug here.

Anyways thank you for reading and answering my topic Miguel.

>miguel medalha via samba [samba at lists.samba.org]
>14.06.19 - 19:05:18
>To: Sascha Brutscher [sascha.brutscher at medicomp.de], samba at
lists.samba.org
>Re: [Samba] Update 4.10.2 to 4.10.4: Cant create files in subdirectorie
anymore
> > ################
> > ### smb.conf ###
> > ### PLEASE NOTE: The options regarding the case sensitivity arent
> usually
> > activated. Normally i leave them on default
> > ### but since i troubleshooted this error for 2 days now i changed
> the
> > conf several times
> > [global]
> > clustering = Yes
> > log level = 10
> > log file = /glusterfs/log.samba
> > netbios name = CLUSTER-01
> > realm = SAMDOM.XYZ
> > registry shares = Yes
> > security = ADS
> > winbind enum groups = Yes
> > winbind enum users = Yes
> > winbind refresh tickets = Yes
> > winbind use default domain = Yes
> > workgroup = SAMDOM
> > idmap config samdom:range = 1000000-1999999
> > idmap config samdom:backend = rid
> > idmap config *:range = 10000-19999
> > idmap config * : backend = tdb
> > case sensitive = No
> > map acl inherit = Yes
> > preserve case = No
> > short preserve case = No
> > vfs objects = acl_xattr
> >
> > [john]
> > #admin users = samdom\administrator
> > comment = admin share
> > kernel share modes = No
> > path = /top1/share
> > read only = No
> > vfs objects = glusterfs
> > glusterfs:loglevel = 1
> > glusterfs:logfile = /glusterfs/glusterfs-gv0.log
> > glusterfs:volume = gv0
> >
> I don't know if this answers the whole of your problem but I find at
> least the following issue:
>
> You declared "vfs objects = acl_xattr" in the global section, but
since
>
> you declared an additional vfs object "vfs objects = glusterfs"
for your
>
> "john" share, you will need to declare both, or "vfs objects
> acl_xattr" won't be active for the share. Under the share, you
must
> declare:
>
>
> vfs objects = acl_xattr glusterfs
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba

On Fri, 2019-06-14 at 19:56 +0200, Sascha Brutscher via samba
wrote:
> You're totally right and after i rechecked my conf i've seen that i
> already set
> vfs objects = acl_xattr gluster
> in my share definition. I just played around with these options to
> see if it helps.
> Neither combination made any difference so i guess my problem isnt
> related to the xattr module,
> it could be related to the gluster module
Absolutely spot on. Please see the following bug:

https://bugzilla.samba.org/show_bug.cgi?id=13872

The fix we did for the above bug broke the existing setup. New fixes
are already in master branch and are on its way to release branches.
> since i did'nt check what would happen if i'd use a local disk
> but using a local disk or another clustered FS is no option for me.
> I'm not sure but i think i stumbled upon a bug here.
> 
> Anyways thank you for reading and answering my topic Miguel.
> 
> 
> > miguel medalha via samba [samba at lists.samba.org]
> > 14.06.19 - 19:05:18
> > To: Sascha Brutscher [sascha.brutscher at medicomp.de], 
> > samba at lists.samba.org
> > Re: [Samba] Update 4.10.2 to 4.10.4: Cant create files in
> > subdirectorie anymore
> > > ################
> > > ### smb.conf ###
> > > ### PLEASE NOTE: The options regarding the case sensitivity arent
> > usually
> > > activated. Normally i leave them on default
> > > ### but since i troubleshooted this error for 2 days now i
> > > changed
> > the
> > > conf several times
> > > [global]
> > > clustering = Yes
> > > log level = 10
> > > log file = /glusterfs/log.samba
> > > netbios name = CLUSTER-01
> > > realm = SAMDOM.XYZ
> > > registry shares = Yes
> > > security = ADS
> > > winbind enum groups = Yes
> > > winbind enum users = Yes
> > > winbind refresh tickets = Yes
> > > winbind use default domain = Yes
> > > workgroup = SAMDOM
> > > idmap config samdom:range = 1000000-1999999
> > > idmap config samdom:backend = rid
> > > idmap config *:range = 10000-19999
> > > idmap config * : backend = tdb
> > > case sensitive = No
> > > map acl inherit = Yes
> > > preserve case = No
> > > short preserve case = No
> > > vfs objects = acl_xattr
> > > 
> > > [john]
> > > #admin users = samdom\administrator
> > > comment = admin share
> > > kernel share modes = No
> > > path = /top1/share
> > > read only = No
> > > vfs objects = glusterfs
> > > glusterfs:loglevel = 1
> > > glusterfs:logfile = /glusterfs/glusterfs-gv0.log
> > > glusterfs:volume = gv0
> > > 
> > I don't know if this answers the whole of your problem but I find
> > at
> > least the following issue:
> > 
> > You declared "vfs objects = acl_xattr" in the global
section, but
> > since
> > 
> > you declared an additional vfs object "vfs objects =
glusterfs" for
> > your
> > 
> > "john" share, you will need to declare both, or "vfs
objects > > acl_xattr" won't be active for the share. Under the
share, you must
> > declare:
> > 
> > 
> > vfs objects = acl_xattr glusterfs
> > 
> > 
> > 
> > --
> > To unsubscribe from this list go to the following URL and read the
> > instructions:  https://lists.samba.org/mailman/options/samba