Bug 1482877 - Extended attributes not supported by the backend storage
Summary: Extended attributes not supported by the backend storage
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 3.11
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-18 09:30 UTC by codeforger
Modified: 2018-07-16 13:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-20 18:24:41 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description codeforger 2017-08-18 09:30:03 UTC
Description of problem:
Geo-replication session becomes faulty after a while of syncing.


Version-Release number of selected component (if applicable):
3.11.2-1

How reproducible:
Setup a session for geo-replication between a local site and a remote one to sync two volumes. Both backend storages are EXT4. The data is backups of servers containing many hard and sumlinks.

Actual results:
The geo-replication session becomes faulty at the same exact point every time I try.

Expected results:
The sync should finish with no errors.

Additional info:
 [fuse-bridge.c:3484:fuse_xattr_cbk] 0-glusterfs-fuse: extended attribute not supported by the backend storage

[2017-08-16 12:57:45.205311] E [repce(/mnt/storage/lapbacks):207:__call__] RepceClient: call 17769:140586894673664:1502888257.97 (entry_ops) failed on peer with OSError
[2017-08-16 12:57:45.205593] E [syncdutils(/mnt/storage/lapbacks):312:log_raise_exception] <top>: FAIL: 
Traceback (most recent call last):
  File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/gsyncd.py", line 204, in main
    main_i()
  File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/gsyncd.py", line 782, in main_i
    local.service_loop(*[r for r in [remote] if r])
  File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/resource.py", line 1656, in service_loop
    g1.crawlwrap(oneshot=True, register_time=register_time)
  File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/master.py", line 600, in crawlwrap
    self.crawl()
  File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/master.py", line 1369, in crawl
    self.process([item[1]], 0)
  File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/master.py", line 1044, in process
    self.process_change(change, done, retry)
  File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/master.py", line 965, in process_change
    failures = self.slave.server.entry_ops(entries)
  File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/repce.py", line 226, in __call__
    return self.ins(self.meth, *a)
  File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/repce.py", line 208, in __call__
    raise res
OSError: [Errno 95] Operation not supported: '.gfid/79614306-8509-4bf2-a2aa-4c14abf58613'
[2017-08-16 12:57:45.235122] I [syncdutils(/mnt/storage/lapbacks):252:finalize] <top>: exiting.
[2017-08-16 12:57:45.279946] I [repce(/mnt/storage/lapbacks):92:service_loop] RepceServer: terminating on reaching EOF.
[2017-08-16 12:57:45.280275] I [syncdutils(/mnt/storage/lapbacks):252:finalize] <top>: exiting.
[2017-08-16 12:57:45.302642] I [gsyncdstatus(monitor):241:set_worker_status] GeorepStatus: Worker Status: Faulty

Comment 1 Shyamsundar 2018-06-20 18:24:41 UTC
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.

Comment 2 Mrten 2018-07-16 10:57:23 UTC
Seeing this in 3.13, upgrading to 4.0 ATM to see if that helps.

Comment 3 Mrten 2018-07-16 13:39:27 UTC
upgrade to 4.0 removed my geo-rep, can't confirm :(


Note You need to log in before you can comment on or make changes to this bug.