<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Kotresh,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks for response! <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>After taking more tests with this specific geo-replication configuration I realized that <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>file extended attributes trusted.gfid and trusted.gfid2path.*** are synced as well during geo replication.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I’m concern about attribute trusted.gfid because value of the attribute has to be unique for glusterfs cluster.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>But this is not a case in my tests. File on master and slave volumes has the same trusted.gfid attribute.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>To handle this issue the geo replication configuration option </span><span style='font-size:10.5pt;font-family:"Helvetica","sans-serif";color:#252525'>sync-xattrs = false was tested on glusterfs version 3.12.3. </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>After changes of the option </span><span style='font-size:10.5pt;font-family:"Helvetica","sans-serif";color:#252525'>from true to false the geo-replication was stopped, volume was stopped, glusterd was stopped, glusterd was started, volume was started and the geo-replication was started again.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Helvetica","sans-serif";color:#252525'>It had no effect on syncing of </span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>trusted.gfid.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>How it is critical to have duplicated gfid’s? Can volume data be corrupted in this case somehow?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Viktor Nosov <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Kotresh Hiremath Ravishankar [mailto:khiremat@redhat.com] <br><b>Sent:</b> Tuesday, January 16, 2018 7:59 PM<br><b>To:</b> Viktor Nosov<br><b>Cc:</b> Gluster Users; jbyers@stonefly.com<br><b>Subject:</b> Re: [Gluster-users] Deploying geo-replication to local peer<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Hi Viktor,<o:p></o:p></p></div><p class=MsoNormal>Answers inline<o:p></o:p></p><div><div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Wed, Jan 17, 2018 at 3:46 AM, Viktor Nosov <<a href="mailto:vnosov@stonefly.com" target="_blank">vnosov@stonefly.com</a>> wrote:<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'>Hi,<br><br>I'm looking for glusterfs feature that can be used to transform data between<br>volumes of different types provisioned on the same nodes.<br>It could be, for example, transformation from disperse to distributed<br>volume.<br>The possible option is to invoke geo-replication between volumes. It seems<br>is works properly.<br>But I'm concern about requirement from Administration Guide for Red Hat<br>Gluster Storage 3.3 (10.3.3. Prerequisites):<br><br>"Slave node must not be a peer of the any of the nodes of the Master trusted<br>storage pool."<o:p></o:p></p><div><p class=MsoNormal> This doesn't limit geo-rep feature in anyway. It's a recommendation. You<o:p></o:p></p></div><div><p class=MsoNormal>can go ahead and use it.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal>Is this restriction is set to limit usage of geo-replication to disaster<br>recovery scenarios only or there is a problem with data synchronization<br>between<br>master and slave volumes?<br><br>Anybody has experience with this issue?<br><br>Thanks for any information!<br><br>Viktor Nosov<br><br><br>_______________________________________________<br>Gluster-users mailing list<br><a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br><a href="http://lists.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://lists.gluster.org/mailman/listinfo/gluster-users</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><br><br clear=all><br>-- <o:p></o:p></p><div><div><div><p class=MsoNormal>Thanks and Regards,<o:p></o:p></p></div><p class=MsoNormal>Kotresh H R<o:p></o:p></p></div></div></div></div></div></div></div></body></html>