Dear List, we actually have a geo-replication setup that replicates different volumes to a server that provides corresponding gluster volumes on top of zfsOnLinux. Unfortunately, the posix acls are not replicated to zfs. I am able to set the acls manually, but they are not transferred. Glusterfs version 6.0 Did someone faces similar issues? Maybe I missed some important stuff here? Any help is appreciated. Regards, Felix On the master side (geo-rep setup): pid_file:/var/run/gluster/gsyncd-volName-slaveHost-volName.pid remote_gsyncd: replica_failover_interval:1 rsync_command:rsync rsync_opt_existing:true rsync_opt_ignore_missing_args:true rsync_options: rsync_ssh_options: slave_access_mount:false slave_gluster_params:aux-gfid-mount acl special_sync_mode: ssh_command:ssh ssh_options:-oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/secret.pem ssh_options_tar:-oPasswordAuthentication=no -oStrictHostKeyChecking=no -i /var/lib/glusterd/geo-replication/tar_ssh.pem ssh_port:22 state_socket_unencoded: stime_xattr_prefix:trusted.glusterfs.0eb1a39b-1236-4e56-9125-7303fa119375.9b7b6507-df29-4742-aea1-7c4573c8f5df sync_acls:true sync_jobs:8 sync_method:rsync sync_xattrs:true tar_command:tar use_meta_volume:true use_rsync_xattrs:false zfs pool information (slave side): [root@host ~]# zfs get all storage/volname NAME PROPERTY VALUE SOURCE storage/volName xattr sa inherited from storage storage/volName acltype posixacl local ________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://bluejeans.com/441850968 Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users