summaryrefslogtreecommitdiffstats
path: root/geo-replication/setup.py
diff options
context:
space:
mode:
authorMilind Changire <mchangir@redhat.com>2016-01-06 21:23:51 +0530
committerAravinda VK <avishwan@redhat.com>2016-03-09 00:26:27 -0800
commit0cb6e6e7020c5a4f2e5c34c6b8cbfa4fdeb45191 (patch)
tree2f2bd9ec7f1b6eabd3e3098b493345e81045eddd /geo-replication/setup.py
parent3122e47e70494fd224f764f86fae29eca16ac06b (diff)
geo-rep: hard-link rename issues on changelog replay
Problem: LINK + RENAME changelog when replayed after worker restart causes stale hard-links to persist since VFS returns success for RENAME if hard-links point to same inode. Solution: Worker detects RENAME being issued on hard-links to the same inode and unlinks the source file-name. Conditionally rename by verifying that the source gfid matches with the on-disk gfid on the slave. Change-Id: I3ff1c30ef79e77503c8b246d46dab8ac3059ccf2 BUG: 1296175 Reviewed-on: http://review.gluster.org/13189 Signed-off-by: Milind Changire <mchangir@redhat.com> Reviewed-on: http://review.gluster.org/13638 Smoke: Gluster Build System <jenkins@build.gluster.com> Tested-by: Aravinda VK <avishwan@redhat.com> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org> CentOS-regression: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Aravinda VK <avishwan@redhat.com>
Diffstat (limited to 'geo-replication/setup.py')
0 files changed, 0 insertions, 0 deletions