<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi, <br>
<br>
Here:
<a class="moz-txt-link-freetext" href="https://github.com/gpfsug/gpfsug-tools/tree/master/bin/rsync">https://github.com/gpfsug/gpfsug-tools/tree/master/bin/rsync</a><br>
<br>
For those of you with Pixit Media / ArcaStream support, just install
our maintained ap-rsync which has this patch and additional fixes
for other 'fun' things that break between GPFS and rsync.<br>
<br>
If anyone wants to contribute to the git repo wave your arms.<br>
<br>
Jez<br>
<br>
<br>
<div class="moz-cite-prefix">On 05/01/17 22:01, Buterbaugh, Kevin L
wrote:<br>
</div>
<blockquote
cite="mid:B946D25F-48B9-48BE-A7E3-E871CACCF60A@vanderbilt.edu"
type="cite">
<pre wrap="">Hi Jaime,
IBM developed a patch for rsync that can replicate ACL’s … we’ve used it and it works great … can’t remember where we downloaded it from, though. Maybe someone else on the list who *isn’t* having a senior moment can point you to it…
Kevin
</pre>
<blockquote type="cite">
<pre wrap="">On Jan 5, 2017, at 3:53 PM, Jaime Pinto <a class="moz-txt-link-rfc2396E" href="mailto:pinto@scinet.utoronto.ca"><pinto@scinet.utoronto.ca></a> wrote:
Does anyone know of a functional standard alone tool to systematically and recursively find and replicate ACLs that works well with GPFS?
* We're currently using rsync, which will replicate permissions fine, however it leaves the ACL's behind. The --perms option for rsync is blind to ACLs.
* The native linux trick below works well with ext4 after an rsync, but makes a mess on GPFS.
% getfacl -R /path/to/source > /root/perms.ac
% setfacl --restore=/root/perms.acl
* The native GPFS mmgetacl/mmputacl pair does not have a built-in recursive option.
Any ideas?
Thanks
Jaime
---
Jaime Pinto
SciNet HPC Consortium - Compute/Calcul Canada
<a class="moz-txt-link-abbreviated" href="http://www.scinet.utoronto.ca">www.scinet.utoronto.ca</a> - <a class="moz-txt-link-abbreviated" href="http://www.computecanada.ca">www.computecanada.ca</a>
University of Toronto
661 University Ave. (MaRS), Suite 1140
Toronto, ON, M5G1M1
P: 416-978-2755
C: 416-505-1477
----------------------------------------------------------------
This message was sent using IMP at SciNet Consortium, University of Toronto.
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
<a class="moz-txt-link-freetext" href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
<a class="moz-txt-link-freetext" href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a>
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<div>
<font color="#000000" face="arial">
<b>Jez Tucker</b><br>
Head of Research and Development, Pixit Media<br>
07764193820 <font color="#FF0000">|</font> <a
href="mailto:jtucker@pixitmedia.com"><a class="moz-txt-link-abbreviated" href="mailto:jtucker@pixitmedia.com">jtucker@pixitmedia.com</a></a><br>
<a href="http://www.pixitmedia.com">www.pixitmedia.com</a> <font
color="#FF0000">|</font> <a
href="https://twitter.com/PixitMedia"><a class="moz-txt-link-abbreviated" href="mailto:Tw:@pixitmedia.com">Tw:@pixitmedia.com</a></a><br>
</font>
</div>
</div>
</body>
</html>
<br>
<div style="font-family:Arial,Helvetica,sans-serif;font-size:1.3em"><a href="http://pixitmedia.com" target="_blank"><img src="http://pixitmedia.com/sig/pixstor_one.png"></a></div><div><font face="Arial, Helvetica, sans-serif" size="3">This email is confidential in that it is intended for the exclusive attention of the addressee(s) indicated. If you are not the intended recipient, this email should not be read or disclosed to any other person. Please notify the sender immediately and delete this email from your computer system. Any opinions expressed are not necessarily those of the company from which this email was sent and, whilst to the best of our knowledge no viruses or defects exist, no responsibility can be accepted for any loss or damage arising from its receipt or subsequent use of this email.</font></div>