<html 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 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Marc, <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The issue with that is that you need multiple passes and things change in between, it also significant increases migration times. You will always miss something or you need to manually correct. The right thing is to have 1 tool that takes care of both, the bulk transfer and the additional attributes. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sven<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:12.0pt;color:black'>From: </span></b><span style='font-size:12.0pt;color:black'><gpfsug-discuss-bounces@spectrumscale.org> on behalf of Marc A Kaplan <makaplan@us.ibm.com><br><b>Reply-To: </b>gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br><b>Date: </b>Monday, October 22, 2018 at 1:09 PM<br><b>To: </b>gpfsug main discussion list <gpfsug-discuss@spectrumscale.org><br><b>Subject: </b>Re: [gpfsug-discuss] Best way to migrate data : mmfind ... mmxcp<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Rather than hack rsync or cp ... I proposed a smallish utility that would copy those extended attributes and ACLs that cp -a just skips over.</span><br><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>This can be done using the documented GPFS APIs that were designed for backup and restore of files.</span><br><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>SMOP and then add it as an option to samples/ilm/mmxcp</span><br><br><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>Sorry I haven't gotten around to doing this ... Seems like a modest sized project... Avoids boiling the ocean and reinventing or hacking rsync.</span><br><br><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>-- marc K</span><br>_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss <o:p></o:p></p></div></body></html>