REVIEW: http://review.gluster.org/5754 (gsyncd / geo-rep: fix "regular file" overloading rename) posted (#1) for review on master by Venky Shankar (vshankar)
REVIEW: http://review.gluster.org/5755 (gsyncd / geo-rep: overload rename with an unlink) posted (#1) for review on master by Venky Shankar (vshankar)
COMMIT: http://review.gluster.org/5754 committed in master by Anand Avati (avati) ------ commit aa292ab99c9db37dd5080aa5d65f24a8887b855b Author: Venky Shankar <vshankar> Date: Wed Aug 21 20:38:09 2013 +0530 gsyncd / geo-rep: fix "regular file" overloading rename entry operation on the slave was using source parent gfid and basename when renames are overloaded to use regular file creation. This patch fixes the issue by using the destination parent gfid and basename for these cases. Change-Id: I1a4e8df7f07905224ce44ef5abd6f180234285ab BUG: 1003800 Tested-by: Amar Tumballi <amarts> Signed-off-by: Venky Shankar <vshankar> Reviewed-on: http://review.gluster.org/5754 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Avra Sengupta <asengupt> Tested-by: Avra Sengupta <asengupt> Reviewed-by: Anand Avati <avati>
COMMIT: http://review.gluster.org/5755 committed in master by Anand Avati (avati) ------ commit 8910136c09e11f651fe846e3f357341b9260930e Author: Venky Shankar <vshankar> Date: Wed Aug 21 16:33:41 2013 +0530 gsyncd / geo-rep: overload rename with an unlink This is certainly a "hack" for cases when after a rename the gfid is unlinked (which is now pointed by a different pargfid/basename). This was osbserved when a file edited (uisng vi/vim) on the glusterfs mount point which has a geo-replication session running. Change-Id: I0a5d9f0f549aa4403671fa1f11e95510142e5720 BUG: 1003800 Signed-off-by: Avra Sengupta <asengupt> Signed-off-by: Venky Shankar <vshankar> Reviewed-by: Amar Tumballi <amarts> Tested-by: Amar Tumballi <amarts> Reviewed-on: http://review.gluster.org/5755 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anand Avati <avati>