Bug 1448541
Summary: | entry failed error with symlink files and dirs using distributed geo replication | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Carl <bettsc> |
Component: | geo-replication | Assignee: | bugs <bugs> |
Status: | CLOSED EOL | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.10 | CC: | avishwan, bettsc, bugs, hostingnuggets, rkavunga, smohan, vnosov |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1350179 | Environment: | |
Last Closed: | 2018-06-20 18:29:10 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: |
Description
Carl
2017-05-05 17:19:37 UTC
I found this bug after running into the exact same problem. Am running Debian 8 (3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux) glusterfs-client 3.10.1-1 glusterfs-common 3.10.1-1 glusterfs-server 3.10.1-1 When first starting geo replication between the hosts. I have some errors exactly as described in the original bug. [2017-05-05 15:22:28.919220] E [master(/bricks/coderepo_data_ssd/coderepo1):762:log_failures] _GMaster: ENTRY FAILED: ({'gfid': '1c3dca94-8de2-4085-a37d-b2b01f7b2752', 'entry': '.gfid/52850b33-ab27-4a04-a172-402e343d4d52/file_name.xml', 'stat': {'atime': 1493932757.5763855, 'gid': 0, 'mtime': 1357762164.0, 'mode': 41471, 'uid': 0}, 'link': 'dir_name/file_name.xml', 'op': 'SYMLINK'}, 2) Was asked on IRC to clone this bug and assign to 3.10 Let me know if I need to provide anymore info. Hi Carl, Thanks for cloning the bug. I will take this bug and will get back to you if any thing needed. Rafi Is anymore information needed? I am happy to provide anything else. Is there any documentation on gluster replication and symlinks? If i re-setup the volume and remove the symlinks before geo-replication starts there are 0 errors. Unfortunately I do need symlinks to be there on other volumes. Thanks, Carl Hi, I initially opened the original bug #1350179 one year ago which got closed without evening being resolved. Now we are one year later and I have upgraded to GlusterFS version 3.8.11 and I still have the exact same problem. This bug makes geo-replication really a pain with GlusterFS as it happens quite often and I don't really understand why this is not being fixed. Thank you in advance for giving this issue higher priority. Best regards, John Is there anything we can adjust in geo-rep to have it see the symlink exists on the replica while this is being looked into? Thanks, Carl This bug reported is against a version of Gluster that is no longer maintained (or has been EOL'd). See https://www.gluster.org/release-schedule/ for the versions currently maintained. As a result this bug is being closed. If the bug persists on a maintained version of gluster or against the mainline gluster repository, request that it be reopened and the Version field be marked appropriately. |