Bug 1176948 - Geo-replication no longer preserves ownership group
Summary: Geo-replication no longer preserves ownership group
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 3.5.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
Assignee: Aravinda VK
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-23 16:09 UTC by David Gibbons
Modified: 2023-09-14 02:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-17 16:24:04 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description David Gibbons 2014-12-23 16:09:21 UTC
Description of problem:
The new version of geo-replication in 3.5.3 seems to not propagate ownership when it replicates.

Version-Release number of selected component (if applicable):
[root@gfs-a-bkp 0018000]# gluster --version
glusterfs 3.5.3 built on Dec 12 2014 07:47:16

How reproducible:
I only have one environment to test with, but the ownership group (gid) is correct on the main cluster and incorrect on the replicated cluster.

Steps to Reproduce:
1. Create geo-replication
2. Observe incorrect permissions and/or ownership on geo-replicated volume
3.

Actual results:
On the geo-replicated volume
[root@gfs-a-bkp 0018000]# ls -lsah
total 64K
4.0K drwxr-xr-x 36 root root 4.0K Dec 15 00:32 .
4.0K drwxrwxrwx 20 root root 4.0K Dec 16 13:45 ..
   0 drwxrwx---  5 root root   57 Dec 14 22:00 0018098
   0 drwxrwx---  2 root root    6 Dec 14 22:00 0018105
   0 drwxrwx---  2 root root    6 Dec 14 22:00 0018181
   0 drwxrwx---  5 root root   57 Dec 14 22:00 0018206
   0 drwxrwx---  6 root root   76 Dec 14 22:00 0018238
   0 drwxrwx---  2 root root   35 Dec 15 03:41 0018241
   0 drwxrwx---  2 root root    6 Dec 14 22:00 0018245
   0 drwxrwx---  6 root root   76 Dec 14 22:00 0018271

Expected results:
On the main cluster volume
[root@gfs-a-1 0018000]# ls -lsah
total 393K
 32K drwxr-xr-x 36 root root   32K Aug 20 15:04 .
 32K drwxrwxrwx 20 root root   32K Oct 31 10:17 ..
4.0K drwxrws---  5 root 34772  456 Jul  1 12:36 0018098
4.0K drwxrws---  2 root 34787   48 Jul  3 02:20 0018105
4.0K drwxrws---  2 root 34933   48 Jul 10 14:45 0018181
4.0K drwxrws---  5 root 34962  456 Jul 11 13:55 0018206
4.0K drwxrws---  6 root 34994  608 Jul 11 22:56 0018238
4.0K drwxrws---  2 root 34998   77 Nov  5 08:31 0018241
4.0K drwxrws---  2 root 35042   48 Jul 14 12:33 0018245
4.0K drwxrws---  6 root 35068  608 Jul 14 14:50 0018271


Additional info:

Comment 1 Aravinda VK 2014-12-29 05:54:46 UTC
Possible duplicate of bz 1104954, back port of patches required for 3.5.x

Comment 2 Aravinda VK 2015-12-29 10:44:01 UTC
This bug is fixed with 3.7 release. Do we need to backport this fix to 3.5.x? We can close this bug if not required in 3.5.x

Comment 3 Niels de Vos 2016-06-17 16:24:04 UTC
This bug is getting closed because the 3.5 is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.

Comment 4 Red Hat Bugzilla 2023-09-14 02:52:40 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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