Not sure if better or worse idea, but I believe robocopy support syncing just the ACLs, so if you do SMB mounts from both sides, that might be an option.
-jf tir. 25. sep. 2018 kl. 20:05 skrev Bryan Banister <[email protected] >: > I have to correct myself, looks like using nfs4_getacl, nfs4_setfacl, > nfs4_editfacl on the NFSv4 client mount of the GPFS file system from a CES > protocol node is working. So could use that to basically crawl the file > system, getting the “outside source” NFSv4 ACL and then applying that to > the file on the NFSv4 client mount of the GPFS file system. > > > > Sorry for confusion, > > -Bryan > > > > *From:* [email protected] < > [email protected]> *On Behalf Of *Bryan Banister > *Sent:* Tuesday, September 25, 2018 12:22 PM > > > *To:* gpfsug main discussion list <[email protected]> > *Subject:* Re: [gpfsug-discuss] replicating ACLs across GPFS's? > > > > [EXTERNAL EMAIL] > > Thanks Simon, > > > > I tried out the older patched version of rsync to see if that would work, > but still not able to preserve ACLs from an non-GPFS source. There was > another thread about this on the user group some time ago as well (2013!), > but doesn’t look like any real solution was found (Copy ACLs from outside > sources > <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.spectrumscale.org%2Fpipermail%2Fgpfsug-discuss%2F2013-October%2F000284.html&data=02%7C01%7Cbbanister%40jumptrading.com%7Cf76e0fae667a49d170c708d6230b72f8%7C11f2af738873424085a3063ce66fc61c%7C1%7C0%7C636734929416724951&sdata=V8g0p4yHweeGY3wOvh2r40QViogULwcmLDT8Ma8I4OE%3D&reserved=0> > ). > > > > I’ve also tried tar | tar, but not luck with that either. > > > > GPFS doesn’t support the nfs4_getacl, nfs4_setfacl, nfs4_editfacl suite of > commands, but maybe that could be added?? > > > > I could maybe hack something up that would basically crawl the “outside > source” namespace, using the nfs4_getacl operation get the NFSv4 ACLs, > parse that output, then attempt to use GPFS `mmputacl` to store the ACL > again. This seems like a horrible way to go, likely prone to mistakes, > tough to validate, nightmare to maintain. > > > > Anybody got better ideas? > > > > Thanks! > > -Bryan > > > > *From:* [email protected] < > [email protected]> *On Behalf Of *Simon Thompson > *Sent:* Friday, September 14, 2018 8:37 AM > *To:* gpfsug main discussion list <[email protected]> > *Subject:* Re: [gpfsug-discuss] replicating ACLs across GPFS's? > > > > [EXTERNAL EMAIL] > > Oh I also heard a rumour of some sort of mmcopy type sample script, but I > can’t see it in samples on 5.0.1-2… > > > > Simon > > > > *From: *<[email protected]> on behalf of Simon > Thompson <[email protected]> > *Reply-To: *"[email protected]" < > [email protected]> > *Date: *Friday, 14 September 2018 at 09:41 > *To: *"[email protected]" <[email protected] > > > *Subject: *Re: [gpfsug-discuss] replicating ACLs across GPFS's? > > > > Last time I built was still against 3.0.9, note there is also a PR in > there which fixes the bug with symlinks. > > > > If anyone wants to rebase the patches against 3.1.3, I’ll happily take a > PR 😊 > > > > Simon > > > > *From: *<[email protected]> on behalf of " > [email protected]" <[email protected]> > *Reply-To: *"[email protected]" < > [email protected]> > *Date: *Friday, 14 September 2018 at 00:33 > *To: *"[email protected]" <[email protected] > > > *Subject: *[gpfsug-discuss] replicating ACLs across GPFS's? > > > > I’m checking in on this thread. Is this patch still working for people > with the latest rsync releases? > > https://github.com/gpfsug/gpfsug-tools/tree/master/bin/rsync > <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgpfsug%2Fgpfsug-tools%2Ftree%2Fmaster%2Fbin%2Frsync&data=02%7C01%7Cbbanister%40jumptrading.com%7Cf76e0fae667a49d170c708d6230b72f8%7C11f2af738873424085a3063ce66fc61c%7C1%7C0%7C636734929416724951&sdata=n%2BDJit691uI4rlkEZy9x89NOcqvlXlUpe%2BzOT6lUfm8%3D&reserved=0> > > > > Thanks! > > -Bryan > > > ------------------------------ > > > Note: This email is for the confidential use of the named addressee(s) > only and may contain proprietary, confidential, or privileged information > and/or personal data. If you are not the intended recipient, you are hereby > notified that any review, dissemination, or copying of this email is > strictly prohibited, and requested to notify the sender immediately and > destroy this email and any attachments. Email transmission cannot be > guaranteed to be secure or error-free. The Company, therefore, does not > make any guarantees as to the completeness or accuracy of this email or any > attachments. This email is for informational purposes only and does not > constitute a recommendation, offer, request, or solicitation of any kind to > buy, sell, subscribe, redeem, or perform any type of transaction of a > financial product. Personal data, as defined by applicable data privacy > laws, contained in this email may be processed by the Company, and any of > its affiliated or related companies, for potential ongoing compliance > and/or business-related purposes. You may have rights regarding your > personal data; for information on exercising these rights or the Company’s > treatment of personal data, please email [email protected]. > > > ------------------------------ > > > Note: This email is for the confidential use of the named addressee(s) > only and may contain proprietary, confidential, or privileged information > and/or personal data. If you are not the intended recipient, you are hereby > notified that any review, dissemination, or copying of this email is > strictly prohibited, and requested to notify the sender immediately and > destroy this email and any attachments. Email transmission cannot be > guaranteed to be secure or error-free. The Company, therefore, does not > make any guarantees as to the completeness or accuracy of this email or any > attachments. This email is for informational purposes only and does not > constitute a recommendation, offer, request, or solicitation of any kind to > buy, sell, subscribe, redeem, or perform any type of transaction of a > financial product. Personal data, as defined by applicable data privacy > laws, contained in this email may be processed by the Company, and any of > its affiliated or related companies, for potential ongoing compliance > and/or business-related purposes. You may have rights regarding your > personal data; for information on exercising these rights or the Company’s > treatment of personal data, please email [email protected]. > > ------------------------------ > > Note: This email is for the confidential use of the named addressee(s) > only and may contain proprietary, confidential, or privileged information > and/or personal data. If you are not the intended recipient, you are hereby > notified that any review, dissemination, or copying of this email is > strictly prohibited, and requested to notify the sender immediately and > destroy this email and any attachments. Email transmission cannot be > guaranteed to be secure or error-free. The Company, therefore, does not > make any guarantees as to the completeness or accuracy of this email or any > attachments. This email is for informational purposes only and does not > constitute a recommendation, offer, request, or solicitation of any kind to > buy, sell, subscribe, redeem, or perform any type of transaction of a > financial product. Personal data, as defined by applicable data privacy > laws, contained in this email may be processed by the Company, and any of > its affiliated or related companies, for potential ongoing compliance > and/or business-related purposes. You may have rights regarding your > personal data; for information on exercising these rights or the Company’s > treatment of personal data, please email [email protected]. > _______________________________________________ > 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
