glusterfs.git/geo-replication/syncdaemon, branch v3.7.5

geo-rep: Do not crash worker on ESTALE

2015-08-06T06:17:25+00:00

Handle ESTALE returned by lstat gracefully
by retrying it. Do not crash the worker.

BUG: 1249547
Change-Id: I57fb9933900153ab41c3d9b73748b1cdaa8d89ca
Reviewed-on: http://review.gluster.org/11772
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Aravinda VK 
Reviewed-by: Venky Shankar 
Signed-off-by: Kotresh HR 
Reviewed-on: http://review.gluster.org/11820
Reviewed-by: Milind Changire

geo-rep: Fix history failure

2015-08-06T05:49:52+00:00

Both ACTIVE and PASSIVE workers register to changelog
at almost same time. When PASSIVE worker becomes ACTIVE,
the start and end time would be current stime and register_time
repectively for history API. Hence register_time would be less
then stime for which history obviously fails. But it will
be successful for the next restart as new register_time > stime.

Fix is to pass current time as the end time to history call
instead of the register_time.

Also improvised the logging for ACTIVE/PASSIVE switching.

BUG: 1247882
Change-Id: I40c582cc32fe29a6c30340ec81a3b5d30e461e71
Reviewed-on: http://review.gluster.org/11524
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Aravinda VK 
Reviewed-by: Venky Shankar 
Signed-off-by: Kotresh HR 
Reviewed-on: http://review.gluster.org/11784
Reviewed-by: Milind Changire

geo-rep: Fix fd referenced before assignment

2015-07-13T02:48:02+00:00

Fix fd reference before assignment in mgmt_lock
function.

BUG: 1240607
Change-Id: Ib8a5207a516eecb55a5f906ff5d49abc98cab2a6
Reviewed-on: http://review.gluster.org/11318
Signed-off-by: Kotresh HR 
Reviewed-on: http://review.gluster.org/11563
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Saravanakumar Arumugam 
Reviewed-by: Milind Changire 
Reviewed-by: Venky Shankar

geo-rep: ignore ESTALE as ENOENT

2015-06-28T14:47:40+00:00

When DHT can't resolve a File it raises ESTALE, ignore ESTALE errors
same as ENOENT after retry.

Affected places:
    Xattr.lgetxattr
    os.listdir
    os.link
    Xattr.lsetxattr
    os.chmod
    os.chown
    os.utime
    os.readlink

BUG: 1236093
Change-Id: I53f8dfa47911da93e0dcc20213afcbb47a14ccd8
Reviewed-On: http://review.gluster.org/11296
Original-Author: Aravinda VK 
Signed-off-by: Kotresh HR 
Reviewed-on: http://review.gluster.org/11430
Tested-by: NetBSD Build System 
Reviewed-by: Milind Changire 
Reviewed-by: Vijay Bellur

geo-rep: Fix geo-rep fanout setup with meta volume

2015-06-25T17:27:28+00:00

Lock filename was formed with 'master volume id'
and 'subvol number'. Hence multiple slaves try
acquiring lock on same file and become PASSIVE
ending up not syncing data. Using 'slave volume id'
in lock filename will fix the issue making lock
file unique across different slaves.

Change-Id: I64c84670a5d9e1b0dfbdeb4479ee6b8e0c6b829e
BUG: 1234898
Reviewed-On: http://review.gluster.org/11367
Signed-off-by: Kotresh HR 
Reviewed-on: http://review.gluster.org/11366
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Saravanakumar Arumugam 
Reviewed-by: Venky Shankar

geo-rep: Fix toggling of use_meta_volume config

2015-06-25T17:15:41+00:00

If meta-volume is deleted and use_meta_volume
is set to false, geo-rep still fails complaining
meta volume is not mounted. The patch fixes that
issue.

BUG: 1234695
Change-Id: I5ec7ad85399b90e85bca1d36750dd3fb29222db9
Reviewe-On: http://review.gluster.org/11358
Signed-off-by: Kotresh HR 
Reviewed-on: http://review.gluster.org/11359
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Saravanakumar Arumugam 
Reviewed-by: Venky Shankar

geo-rep: Ignore ESTALE during unlink/rmdir

2015-06-01T06:38:15+00:00

during unlink/rmdir of Parent_GFID/Basename, if parent
directory does not exists. Parent GFID will not get resolved
and DHT raises ESTALE instead of ENOENT.

Now ESTALE errors ignored during unlink/rmdir

BUG: 1223286
Change-Id: If275c89fb9fc7d16004550805a4cd65be818540d
Signed-off-by: Aravinda VK 
Reviewed On: http://review.gluster.org/#/c/10837/
Reviewed-on: http://review.gluster.org/10913
Tested-by: NetBSD Build System 
Tested-by: Gluster Build System 
Reviewed-by: Kotresh HR 
Reviewed-by: Venky Shankar

geo-rep: Fix Data counter issue in status

2015-05-31T14:44:20+00:00

ENTRY and META operations executed sequentially, DATA operations
are handled async, increment happens when a changelog parsed.
Decrement happens after the sync of all files.

files_in_batch was reset multiple times in batch instead of once.

BUG: 1224100
Change-Id: I87617f2fd5f4d3221a1c9f9d5a8efb0686c42bbe
Signed-off-by: Aravinda VK 
Reviewed On: http://review.gluster.org/#/c/10911/
Reviewed-on: http://review.gluster.org/10912
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System 
Reviewed-by: Venky Shankar

geo-rep: Disable xattrs and acls support with tar_ssh

2015-05-29T09:02:32+00:00

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/" 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 
Reviewed-on: http://review.gluster.org/10899
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System
Reviewed-by: Aravinda VK

geo-rep: Fix corrupt gsyncd output

2015-05-09T09:18:04+00:00

When gsyncd fails with Python traceback, glusterd fails
parsing gsyncd output and shows error.

BUG: 1219938
Change-Id: Ic32fd897c49a5325294a6588351b539c6e124338
Signed-off-by: Aravinda VK 
Reviewed-on: http://review.gluster.org/10694
Reviewed-on: http://review.gluster.org/10695
Tested-by: Gluster Build System 
Tested-by: NetBSD Build System
Reviewed-by: Kotresh HR 
Reviewed-by: Vijay Bellur