Bug 1582394

Summary: [geo-rep]: False error message in geo-rep logs (rsnapshot usecase)
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Rochelle <rallan>
Component: geo-replicationAssignee: Kotresh HR <khiremat>
Status: CLOSED ERRATA QA Contact: Rahul Hinduja <rhinduja>
Severity: low Docs Contact:
Priority: unspecified    
Version: rhgs-3.4CC: amukherj, csaba, rhs-bugs, sheggodu, storage-qa-internal
Target Milestone: ---Keywords: Rebase
Target Release: RHGS 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-6.0-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-30 12:19:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1696807    

Description Rochelle 2018-05-25 05:49:42 UTC
Description of problem:
=======================
Operations done by rsnapshot with geo-replication threw the following false/misleading error

[2018-05-24 07:11:24.606070] I [master(/rhs/brick1/b1):842:fix_possible_entry_failures] _GMaster: Fixing gfid mismatch in slave.  Deleting the entry    retry_count=1   entry=({'stat': {'atime': 1527145868.474402
2, 'gid': 0, 'mtime': 1527145861.3702629, 'mode': 41471, 'uid': 0}, 'entry1': '.gfid/ca02c73a-71fb-405b-b9f1-73d4d2ff5c16/a_symlink', 'gfid': 'd8b9c916-09ef-4b1e-ba56-56686e2cc54c', 'link': '/does/not/exist2', '
entry': '.gfid/ca02c73a-71fb-405b-b9f1-73d4d2ff5c16/.a_symlink.14544', 'op': 'RENAME'}, 17, {'gfid_mismatch': True, 'dst': True, 'slave_isdir': False, 'slave_gfid': 'ed9c6a1a-7eee-4905-bd8b-7bb8343ded57'})
[2018-05-24 07:11:24.606492] E [master(/rhs/brick1/b1):849:fix_possible_entry_failures] _GMaster: Entry cannot be fixed in slave due to GFID mismatch, find respective path for the GFID and trigger sync       gfid=ed9c6a1a-7eee-4905-bd8b-7bb8343ded57
[2018-05-24 07:11:24.615130] I [master(/rhs/brick1/b1):855:fix_possible_entry_failures] _GMaster: Sucessfully fixed entry ops with gfid mismatch


Data synced as expected hence it's a false error message

Version-Release number of selected component (if applicable):
=============================================================
[root@dhcp42-29 master]# rpm -qa | grep gluster
vdsm-gluster-4.19.43-2.3.el7rhgs.noarch
glusterfs-libs-3.12.2-11.el7rhgs.x86_64
glusterfs-geo-replication-3.12.2-11.el7rhgs.x86_64
glusterfs-fuse-3.12.2-11.el7rhgs.x86_64
libvirt-daemon-driver-storage-gluster-3.9.0-14.el7_5.4.x86_64
glusterfs-client-xlators-3.12.2-11.el7rhgs.x86_64
glusterfs-server-3.12.2-11.el7rhgs.x86_64
gluster-nagios-common-0.2.4-1.el7rhgs.noarch
glusterfs-3.12.2-11.el7rhgs.x86_64
glusterfs-cli-3.12.2-11.el7rhgs.x86_64
glusterfs-rdma-3.12.2-11.el7rhgs.x86_64
gluster-nagios-addons-0.2.10-2.el7rhgs.x86_64
glusterfs-api-3.12.2-11.el7rhgs.x86_64
python2-gluster-3.12.2-11.el7rhgs.x86_64



How reproducible:
=================
2/2


Steps to Reproduce:
===================
1. create volume on master and slave and setup geo-replication between them
2. mount master volume and cd to it (nfs or fuse doesn't make a difference)
3. simulate a rsnapshot run that updates a symlink like this:

mkdir /tmp/symlinkbug
ln -f -s /does/not/exist /tmp/symlinkbug/a_symlink
rsync -a /tmp/symlinkbug ./
cp -al symlinkbug symlinkbug.0
ln -f -s /does/not/exist2 /tmp/symlinkbug/a_symlink
rsync -a /tmp/symlinkbug ./
cp -al symlinkbug symlinkbug.1


Actual results:
===============
Geo-rep logs throw "Entry cannot be fixed in slave due to GFID mismatch"

Expected results:
=================
There should be no misleading errror

Comment 12 errata-xmlrpc 2019-10-30 12:19:38 UTC
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.

https://access.redhat.com/errata/RHEA-2019:3249