[gpfsug-discuss] replicating ACLs across GPFS's?

[Jez Tucker]

Some of the 'fun things' being such as that very issue.

On 06/01/17 07:17, Simon Thompson (Research Computing - IT Services) wrote:
> Just a cautionary note, it doesn't work with symlinks as it fails to get the acl and so doesn't copy the symlink.
>
> So you may want to run a traditional rsync after just to get all your symlinks on place. (having been using this over the Christmas period to merge some filesets with acls...)
>
> Simon
> ________________________________________
> From: gpfsug-discuss-bounces at spectrumscale.org [gpfsug-discuss-bounces at spectrumscale.org] on behalf of Jaime Pinto [pinto at scinet.utoronto.ca]
> Sent: 06 January 2017 02:16
> To: gpfsug main discussion list; Laurence Horrocks-Barlow
> Cc: support at scinet.utoronto.ca
> Subject: Re: [gpfsug-discuss] replicating ACLs across GPFS's?
>
> Great guys!!!
> Just what I was looking for.
> Everyone is always so helpful on this forum.
> Thanks a lot.
> Jaime
>
> Quoting "Laurence Horrocks-Barlow" <laurence at qsplace.co.uk>:
>
>> Are you talking about the GPFSUG github?
>>
>> https://github.com/gpfsug/gpfsug-tools
>>
>> The patched rsync there I believe was done by Orlando.
>>
>> -- Lauz
>>
>>
>> On 05/01/2017 22:01, Buterbaugh, Kevin L wrote:
>>> 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
>>>
>>>> On Jan 5, 2017, at 3:53 PM, Jaime Pinto <pinto at scinet.utoronto.ca> 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
>>>> www.scinet.utoronto.ca - www.computecanada.ca
>>>> 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
>>>> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
>>> _______________________________________________
>>> gpfsug-discuss mailing list
>>> gpfsug-discuss at spectrumscale.org
>>> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
>> _______________________________________________
>> gpfsug-discuss mailing list
>> gpfsug-discuss at spectrumscale.org
>> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
>>
>
> ----------------------------------------------------------------
> This message was sent using IMP at SciNet Consortium, University of Toronto.
>
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss
> _______________________________________________
> gpfsug-discuss mailing list
> gpfsug-discuss at spectrumscale.org
> http://gpfsug.org/mailman/listinfo/gpfsug-discuss

-- 
*Jez Tucker*
Head of Research and Development, Pixit Media
07764193820 | jtucker at pixitmedia.com <mailto:jtucker at pixitmedia.com>
www.pixitmedia.com <http://www.pixitmedia.com> | Tw:@pixitmedia.com 
<https://twitter.com/PixitMedia>

-- 
 <http://pixitmedia.com>
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20170106/66d119ad/attachment-0002.htm>