Red Hat Bugzilla – Bug 986929
dist-geo-rep: create/link/unlink results in data loss on the slave
Last modified: 2014-08-24 20:50:13 EDT
Description of problem:
An operation like the following would result in gsyncd
trying to retry the CHANGELOG again and again:
CREATE GFID PARGFID/BNAME
LINK PARGFID/NAME PARGFID1/BNAME1
Since entry operations are performed first, the object
represented by PARGFID/BNAME (GFID) is no longer present
on the slave. But beacuse of an hardlink operation the
object still exist on the master. This causes data loss
on the slave (for the hardlink).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
0. Start Geo-replication b/w master and slave
1. Create a file on master and write data to the file.
2. Create an hardlink to the above file
3. unlink the file created in Step 1
The hardlink is created on the slave but had 0 bytes (empty file).
master and slave should be in sync.
verified on glusterfs-188.8.131.52rhs-1.el6rhs.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
For information on the advisory, and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.