[Bugs] [Bug 1510342] Not all files synced using geo-replication
bugzilla at redhat.com
bugzilla at redhat.com
Fri Feb 2 06:46:57 UTC 2018
https://bugzilla.redhat.com/show_bug.cgi?id=1510342
--- Comment #17 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/19217 committed in release-3.12 by "jiffin
tony Thottan" <jthottan at redhat.com> with a commit message- geo-rep: Fix data
sync issue during hardlink, rename
Problem:
The data is not getting synced if master witnessed
IO as below.
1. echo "test_data" > f1
2. ln f1 f2
3. mv f2 f3
4. unlink f1
On master, 'f3' exists with data "test_data" but on
slave, only f3 exists with zero byte file without
backend gfid link.
Cause:
On master, since 'f2' no longer exists, the hardlink
is skipped during processing. Later, on trying to sync
rename, since source ('f2') doesn't exist, dst ('f3')
is created with same gfid. But in this use case, it
succeeds but backend gfid would not have linked as 'f1'
exists with the same gfid. So, rsync would fail with
ENOENT as backend gfid is not linked with 'f3' and 'f1'
is unlinked.
Fix:
On processing rename, if src doesn't exist on slave,
don't blindly create dst with same gfid. The gfid
needs to be checked, if it exists, hardlink needs
to be created instead of mknod.
Thanks Aravinda for helping in RCA :)
> Change-Id: I5af4f99798ed1bcb297598a4bc796b701d1e0130
> Signed-off-by: Kotresh HR <khiremat at redhat.com>
> BUG: 1512483
> Reporter: dimitri.ars at gmail.com
(cherry picked from commit 6e2ce37341e5d600d8fd5648b39eec0dbdbe45ad)
Change-Id: I5af4f99798ed1bcb297598a4bc796b701d1e0130
Signed-off-by: Kotresh HR <khiremat at redhat.com>
BUG: 1510342
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=unND9aktTD&a=cc_unsubscribe
More information about the Bugs
mailing list