[Bugs] [Bug 1223644] [geo-rep]: With tarssh the file is created at slave but it doesnt get sync

bugzilla at redhat.com bugzilla at redhat.com
Fri May 29 09:02:38 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1223644



--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/10899 committed in release-3.7 by Venky
Shankar (vshankar at redhat.com) 
------
commit 31d494d4f0a4bf7fa588efb57f8dc5e8788c7758
Author: Kotresh HR <khiremat at redhat.com>
Date:   Thu May 21 11:55:03 2015 +0530

    geo-rep: Disable xattrs and acls support with tar_ssh

    Geo-rep can't sync xattrs and acls with tar over ssh
    for following reasons.

    Issue 1: xattrs doesn't sync with tar over ssh.

    Reason: untar doesn't respect '--overwrite' option when used along
            with '--xattrs'. So it sends unlink if the file exists on
            destination and re-creates afresh. But all entry operations
            are banned in aux-gfid-mount as it may lead to gfid-mismatch.
            Hence fails with EPERM. This happens only when some xattr is
            set on a file in master volume.

    Issue2: acls on directories does not sync with tar over ssh.

    Reason: tar tries to opendir ".gfid/<gfid1>" and is not supported
            by gfid-access-translator as readirp can't be handled on
            virtual inodes and hence fails with ENOTSUP where as it syncs
            for files.

    Since the issue is with tar commmand it self and nothing could be
    done from gluster side, disabling xattr and acls support with tar
    over ssh option.

    Geo-rep can sync xattrs and acls with 'rsync' as the sync engine.

    BUG: 1223644
    Change-Id: Ieba9e749ddbc41683b58ed8b1cc2ca50517fe58b
    Reviewed On: http://review.gluster.org/#/c/10873
    Signed-off-by: Kotresh HR <khiremat at redhat.com>
    Reviewed-on: http://review.gluster.org/10899
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Tested-by: NetBSD Build System
    Reviewed-by: Aravinda VK <avishwan at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=TidKUhCZGC&a=cc_unsubscribe


More information about the Bugs mailing list