Hi Ravi,
Many thanks for the super-quick turnaround on this!
Didn't know about this one quirk os chown, so thanks for that as well.
Anirban
On Thursday, 30 January 2014 9:22 AM, Ravishankar N <[email protected]>
wrote:
Hi Anirban,
Thanks for taking the time off to file the bugzilla bug report.
The fix has been sent for review upstream
(http://review.gluster.org/#/c/6862/). Once it is merged, I will backport
it to 3.4 as well.
Regards,
Ravi
On 01/28/2014 02:07 AM, Chalcogen wrote:
Hi,
I am working on a twin-replicated setup (server1 and server2)
with glusterfs 3.4.0. I perform the following steps:
1. Create a distributed volume 'testvol' with the XFS brick
server1:/brick/testvol on server1, and mount it using the glusterfs native
client at /testvol.
2. I copy the following file to /testvol:
server1:~$ ls -l /bin/su
-rwsr-xr-x 1 root root 84742 Jan 17 2014 /bin/su
server1:~$ cp -a /bin/su /testvol
3. Within /testvol if I list out the file I just copied, I find its
attributes intact.
4. Now, I add the XFS brick server2:/brick/testvol.
server2:~$ gluster volume add-brick testvol replica 2 server2:/brick/testvol
At this point, heal kicks in and the file is replicated on
server 2.
5. If I list out su in testvol on either server now, now, this is what
I see.
server1:~$ ls -l /testvol/su
-rwsr-xr-x 1 root root 84742 Jan 17 2014 /bin/su
server2:~$ ls -l /testvol/su
-rwxr-xr-x 1 root root 84742 Jan 17 2014 /bin/suThat is, the 's' file mode
gets changed to plain 'x' - meaning, all the attributes are not preserved upon
heal completion. Would you consider this a bug? Is the behavior different on a
higher release?
Thanks a lot.
Anirban
_______________________________________________
Gluster-users mailing list [email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users_______________________________________________
Gluster-users mailing list
[email protected]
http://supercolony.gluster.org/mailman/listinfo/gluster-users
