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

[bugzilla at redhat.com]

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

            Bug ID: 1223644
           Summary: [geo-rep]: With tarssh the file is created at slave
                    but it doesnt get sync
           Product: GlusterFS
           Version: 3.7.0
         Component: geo-replication
          Keywords: Regression
          Severity: urgent
          Assignee: bugs at gluster.org
          Reporter: khiremat at redhat.com
                CC: aavati at redhat.com, avishwan at redhat.com,
                    bugs at gluster.org, csaba at redhat.com,
                    gluster-bugs at redhat.com, khiremat at redhat.com,
                    nlevinki at redhat.com, rhinduja at redhat.com,
                    storage-qa-internal at redhat.com
        Depends On: 1222776, 1223642



+++ This bug was initially created as a clone of Bug #1223642 +++

+++ This bug was initially created as a clone of Bug #1222776 +++

Description of problem:
=======================

When we are using sync option as tarssh "use-tarssh true". Whenever the file is
created at master volume, the respective entry gets created at the slave but
the actual sync doesn't happen.

At master volume:
=================

[root at wingo master]# pwd
/mnt/master
[root at wingo master]# ls
hosts  hosts.allow
[root at wingo master]# cat *
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
#
# hosts.allow    This file contains access rules which are used to
#        allow or deny connections to network services that
#        either use the tcp_wrappers library or that have been
#        started through a tcp_wrappers-enabled xinetd.
#
#        See 'man 5 hosts_options' and 'man 5 hosts_access'
#        for information on rule syntax.
#        See 'man tcpd' for information on tcp_wrappers
#
[root at wingo master]# 


At slave volume:
================

[root at wingo slave]# pwd
/mnt/slave
[root at wingo slave]# ls
hosts  hosts.allow
[root at wingo slave]# cat *
[root at wingo slave]# cat hosts
[root at wingo slave]# cat hosts.allow 
[root at wingo slave]# 

Version-Release number of selected component (if applicable):
=============================================================

How reproducible:
=================

Always


Steps to Reproduce:
===================
1. Create a master cluster
2. Create and Start the master volume 
3. Create a slave cluster
4. Create ans Start the slave volume
5. Create and start gluster_shared_storage volume
6. Mount gluster_shared_storage at /var/run/gluster/shared_storage on all the
master nodes participating in master volume.
7. Create the geo-rep session
8. Set the config option use_meta_volume to true
9. Set the config option use_tarssh to true
10. Start the geo-rep session
11. Mount the master volume to client and create a file
12. Mount the slave volume
13. Check the files on master and slave volume 


Actual results:
===============

Files that are in master gets created at slave with no content. (The first
phase of creation the entry is successful but the actual sync doesn't happen)


Expected results:
=================

The files should actually sync.

--- Additional comment from Kotresh HR on 2015-05-21 02:14:12 EDT ---

The issue is with recent enhancement to sync extended attributes in
geo-replication.

The --overwrite option being usind with tar command is not in effect when 
--xattrs option of tar command is used to sync xattrs. The consequence being if
file exists on destination, it does not overwrite, it tries to unlink (which
fails in gfid-access translator as entries are banned on aux-gfid-mount) hence
fails. gfid-access translator doesn't allow because it may lead to gfid
inconsistency.

NOTE: --overwrite option is used in tar over ssh mode to keep gfids intact.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1222776
[Bug 1222776] [geo-rep]: With tarssh the file is created at slave but it
doesnt get sync
https://bugzilla.redhat.com/show_bug.cgi?id=1223642
[Bug 1223642] [geo-rep]: With tarssh the file is created at slave but it
doesnt get sync
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.