From d685e4238fafba8f58bf01174c79cb5ca35203e5 Mon Sep 17 00:00:00 2001 From: Kotresh HR Date: Wed, 26 Jul 2017 08:09:31 -0400 Subject: [PATCH] geo-rep: Fix syncing of self healed hardlinks Problem: In a distribute replicate volume, if the hardlinks are created when a subvolume is down, it gets healed from other subvolume when it comes up. If this subvolume becomes ACTIVE in geo-rep there are chances that those hardlinks won't be synced to slave. Cause: AFR can't detect hardlinks during self heal. It just create those files using mknod and the same is recorded in changelog. Geo-rep processes these mknod and ignores it as it finds gfid already on slave. Solution: Geo-rep should process the mknod as link if the gfid already exists on slave. Change-Id: I2f721b462b38a74c60e1df261662db4b99b32057 BUG: 1475308 Signed-off-by: Kotresh HR Reviewed-on: https://review.gluster.org/17880 Smoke: Gluster Build System CentOS-regression: Gluster Build System Reviewed-by: Aravinda VK --- geo-replication/syncdaemon/resource.py | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/geo-replication/syncdaemon/resource.py b/geo-replication/syncdaemon/resource.py index 275e9fd29..a608944f9 100644 --- a/geo-replication/syncdaemon/resource.py +++ b/geo-replication/syncdaemon/resource.py @@ -797,6 +797,14 @@ class Server(object): if isinstance(st, int): blob = entry_pack_reg( gfid, bname, e['mode'], e['uid'], e['gid']) + # Self healed hardlinks are recorded as MKNOD. + # So if the gfid already exists, it should be + # processed as hard link not mknod. + elif op in ['MKNOD']: + cmd_ret = errno_wrap(os.link, + [slink, entry], + [ENOENT, EEXIST], [ESTALE]) + collect_failure(e, cmd_ret) elif op == 'MKDIR': slink = os.path.join(pfx, gfid) st = lstat(slink)