Hello. There are two servers on samba. Balls are made on glusterfs. samba works through ctdb. If you connect a vfs ball with the glusterfs_vfs module, then the necessary ACLs are not installed on the root of Windows. Folder validity inheritance. If a mounted glusterfs disk is made into a samba ball, then ACLs are put on the root without problems. Is there a way to solve this problem? That is, set normal ACLs through the vfs module.
To make it more clear configs. /etc/samba/smb.conf:
[global] security = ads clustering = yes vfs objects = acl_xattr map acl inherit = yes store dos attributes = yes [gluster-samba] vfs objects = glusterfs glusterfs:volfile_server = nt-50.npc-mka.ru glusterfs:volume = samba glusterfs:logfile = /var/log/samba/glusterfs-samba.%M.log glusterfs:loglevel = 10 kernel share modes = No path = / read only = No writeable = Yes [samba] path = /media/samba read only = No public = No writable = Yes On gluster-samba, you just have to steer the ACL. samba is mounted to the system:
nt-50:/samba on /media/samba type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,allow_other,max_read=131072) So if you connect to this server on Windows and go into shared folders, then on samba, security rights are set up without problems and saved. And on gluster-samba are put without problems, but are not saved. Although rights are placed on separate folders, but only r, rw, rwx, that is, add. Attributes are not saved.
