Geo-rep expects gfid to be same on both master and slave.
Geo-rep fails to sync the entry on to slave because a file already exists with different gfid.
Changelogs of each brick are processed parallely. There could be race where already deleted file on master is still present on slave and fails sync the new file with same name created on master.
The entry failures because of gfid mismatch are gracefully handled by verifying it on the master.