[Bugs] [Bug 1448541] New: entry failed error with symlink files and dirs using distributed geo replication

bugzilla at redhat.com bugzilla at redhat.com
Fri May 5 17:19:37 UTC 2017


https://bugzilla.redhat.com/show_bug.cgi?id=1448541

            Bug ID: 1448541
           Summary: entry failed error with symlink files and dirs using
                    distributed geo replication
           Product: GlusterFS
           Version: 3.10
         Component: geo-replication
          Severity: medium
          Assignee: bugs at gluster.org
          Reporter: bettsc at interstatecargo.com
                CC: avishwan at redhat.com, bugs at gluster.org,
                    hostingnuggets at gmail.com, smohan at redhat.com,
                    vnosov at stonefly.com



+++ This bug was initially created as a clone of Bug #1350179 +++

Description of problem:
Distributed geo-replication generates errors in its geo-replication geo.log
file on tge master when replicating symlinked directories or files. An example 
of such an error taken from this log file:

[2016-06-25 23:57:58.566375] E [master(/data/myvolume/brick):784:log_failures]
_GMaster: ENTRY FAILED: ({'gfid': 'f2156f11-505a-4bb7-a697-8da4a97e622d',
'entry': '.gfid/aa5198e7-fc88-4135-863b-a69e451df450/vphn.c', 'stat': {'atime':
1466618772.882145, 'gid': 0, 'mtime': 1462143151.0, 'mode': 41471, 'uid': 0},
'link': '../../../../../arch/powerpc/mm/vphn.c', 'op': 'SYMLINK'}, 2)

This error is also reported in the "gluster volume geo-replication status
detail" command under the FAILURES column. The number reported under the
FAILURES count matches the number of error lines found in the log file
mentioned above.

Nevertheless the symlinked files and directories exists on the slave so they
have been replicated but still an error is reported.

Version-Release number of selected component (if applicable):
GlusterFS 3.7.11 on Debian 8

How reproducible:
I just took a linux kernel tarball which contains a few symbolic links of files
and directories and unpacked it onto my volume and then started geo-replication
for the first time.

Steps to Reproduce:
1. setup two nodes replica volume
2. unpack linux-4.6-rc6.tar.xz (taken from kernel.org) onto that volume
(contains 23 symbolic links)
3. setup distributed geo-replication to slave node and start geo-replication

Actual results:
23 FAILURES reported under the status details of geo replication command and 23
errors in the geo.log file on the master

Expected results:
0 FAILURES and 0 error lines in the geo.log log file

Additional info:
Using Debian 8.5 on all nodes

--- Additional comment from Kaushal on 2017-03-08 05:54:10 EST ---

This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been
performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug
against the newer release.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list