Bug 1327045 - [geo-rep]: rsync should not try to sync internal xattrs
Summary: [geo-rep]: rsync should not try to sync internal xattrs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: geo-replication
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: RHGS 3.3.0
Assignee: Mohammed Rafi KC
QA Contact: Rochelle
URL:
Whiteboard:
Depends On:
Blocks: 1417147
TreeView+ depends on / blocked
 
Reported: 2016-04-14 07:26 UTC by Rahul Hinduja
Modified: 2017-09-21 04:53 UTC (History)
11 users (show)

Fixed In Version: glusterfs-3.8.4-24
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1353952 (view as bug list)
Environment:
Last Closed: 2017-09-21 04:25:52 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2774 0 normal SHIPPED_LIVE glusterfs bug fix and enhancement update 2017-09-21 08:16:29 UTC

Description Rahul Hinduja 2016-04-14 07:26:24 UTC
Description of problem:
=======================

Found following errors in the geo-replication logs while the rsync retries the incomplete sync.

[2016-04-13 14:12:50.607055] E [resource(/rhs/brick1/b1):991:rsync] SSH: SYNC Error(Rsync): rsync: rsync_xal_set: lsetxattr(""/proc/1906/cwd/.gfid/00d486f4-97e0-44eb-9049-49c93df7f776"","trusted.glusterfs.fb163479-1572-4dc4-96d3-faf94715ef9f.xtime") failed: Operation not permitted (1)
[2016-04-13 14:12:50.607678] E [resource(/rhs/brick1/b1):991:rsync] SSH: SYNC Error(Rsync): rsync: rsync_xal_set: lsetxattr(""/proc/1906/cwd/.gfid/00d8cb77-c512-4747-9cfa-2e7a7289e280"","trusted.glusterfs.fb163479-1572-4dc4-96d3-faf94715ef9f.xtime") failed: Operation not permitted (1)
[2016-04-13 14:12:50.607942] E [resource(/rhs/brick1/b1):991:rsync] SSH: SYNC Error(Rsync): rsync: rsync_xal_set: lsetxattr(""/proc/1906/cwd/.gfid/01410949-268f-4a85-b716-fa66f3ac78df"","trusted.glusterfs.fb163479-1572-4dc4-96d3-faf94715ef9f.xtime") failed: Operation not permitted (1)
[2016-04-13 14:12:50.608335] E [resource(/rhs/brick1/b1):991:rsync] SSH: SYNC Error(Rsync): rsync: rsync_xal_set: lsetxattr(""/proc/1906/cwd/.gfid/0148c89c-0cf5-4169-9e0e-a5e88890a629"","trusted.glusterfs.fb163479-1572-4dc4-96d3-faf94715ef9f.xtime") failed: Operation not permitted (1)
[2016-04-13 14:12:50.608597] E [resource(/rhs/brick1/b1):991:rsync] SSH: SYNC Error(Rsync): rsync: rsync_xal_set: lsetxattr(""/proc/1906/cwd/.gfid/0188e977-db73-4ed2-9093-4943539afb8e"","trusted.glusterfs.fb163479-1572-4dc4-96d3-faf94715ef9f.xtime") failed: Operation not permitted (1)
[2016-04-13 14:12:50.608838] E [resource(/rhs/brick1/b1):991:rsync] SSH: SYNC Error(Rsync): rsync: rsync_xal_set: lsetxattr(""/proc/1906/cwd/.gfid/0193043a-6f26-43ed-84e5-7f3e0e977ecd"","trusted.glusterfs.fb163479-1572-4dc4-96d3-faf94715ef9f.xtime") failed: Operation not permitted (1)
[2016-04-13 14:12:50.609113] E [resource(/rhs/brick1/b1):991:rsync] SSH: SYNC Error(Rsync): rsync: rsync_xal_set: lsetxattr(""/proc/1906/cwd/.gfid/01d8abfd-d870-465f-883b-264aa8009ced"","trusted.glusterfs.fb163479-1572-4dc4-96d3-faf94715ef9f.xtime") failed: Operation not permitted (1)
[2016-04-13 14:12:50.609329] E [resource(/rhs/brick1/b1):991:rsync] SSH: SYNC Error(Rsync): rsync: rsync_xal_set: lsetxattr(""/proc/1906/cwd/.gfid/020ed975-cd04-4a16-b1e4-fad344256dbc"","trusted.glusterfs.fb163479-1572-4dc4-96d3-faf94715ef9f.xtime") failed: Operation not permitted (1)

rsync should not try syncing internal xattrs. 



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

glusterfs-3.7.9-1.el7rhgs.x86_64


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

Steps Carried:
1. Ran geo-replication automated cases once with root and once with non-root.
2. Worker kept going ACTIVE => PASSIVE => ACTIVE due to input/output error
3. Incomplete changelogs were picked up for syncing which reported these errors in huge numbers

Comment 6 Kotresh HR 2017-02-23 11:29:02 UTC
Upstream Patch:

https://review.gluster.org/#/c/14880/

Comment 8 Mohammed Rafi KC 2017-04-24 07:40:05 UTC
downstream patch : https://code.engineering.redhat.com/gerrit/103428

Comment 10 Rochelle 2017-07-25 09:19:43 UTC
A non-root set up of geo-replication was created on 3.2.0 and 3.3.0 builds with the following steps :

1. IO was created on the master mount :
for i in {1..5}; do cp -rf /etc etc.$i; done

2. Wait for IO to complete on the master
3. Start the geo-replication session (Started with hybrid crawl)
4. All the files were synced to slave 

In 3.2.0: Incomplete sync was observed (glusterfs-geo-replication-3.8.4-18.6.el7rhgs.x86_64)
In 3.3.0: There was no incomplete sync

verified with : glusterfs-geo-replication-3.8.4-35.el7rhgs.x86_64

Moving this bug to verified.

Comment 12 errata-xmlrpc 2017-09-21 04:25:52 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/RHBA-2017:2774

Comment 13 errata-xmlrpc 2017-09-21 04:53:56 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/RHBA-2017:2774


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