Bug 1565399

Summary: [GSS] geo-rep in faulty session due to OSError: [Errno 95] Operation not supported
Product: Red Hat Gluster Storage Reporter: Oonkwee Lim_ <olim>
Component: geo-replicationAssignee: Kotresh HR <khiremat>
Status: CLOSED ERRATA QA Contact: Rochelle <rallan>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rhgs-3.3CC: amukherj, atoborek, bkunal, csaba, hamiller, khiremat, mmuir, olim, rallan, rhs-bugs, srmukher, ssaha, storage-qa-internal
Target Milestone: ---   
Target Release: RHGS 3.4.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: glusterfs-3.12.2-9 Doc Type: Bug Fix
Doc Text:
Previously, if symlinks were created by a non-privileged user pointing to current directory on the master volume, geo-replication failed to sync them to slave. Instead of setting the permissions on the symlink, it used to dereference the symlink pointing to the virtual directory ".gfid" and failed with "Operation not supported" error. With this fix, geo-replication does not dereference symlink while setting permissions on file and syncs symlinks created by non-privileged user pointing to the current directory.
Story Points: ---
Clone Of:
: 1567209 (view as bug list) Environment:
Last Closed: 2018-09-04 06:46:01 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:
Bug Depends On: 1567209    
Bug Blocks: 1503138, 1577845    

Comment 31 Srijita Mukherjee 2018-09-03 15:45:27 UTC
have updated the doc text. Kindly review and confirm

Comment 34 errata-xmlrpc 2018-09-04 06:46:01 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.


Comment 35 Olek Toborek 2018-09-11 12:45:35 UTC
*** Bug 1611838 has been marked as a duplicate of this bug. ***