Hi Marc, this was meant to be more a joke than a 'wish' - but it would be interesting for us (with the case of several millions of files having the same ACL) if there are ways/plans to treat ACLs more referenced from each of these files and having a mechanism to treat all of them in a single operation.
-- Martin > On 7 Aug, 2015, at 23:21, Marc A Kaplan <[email protected]> wrote: > > You asked: > > "your description of the ACL implementation looks like each file has some > sort of reference to the ACL - so multiple files could reference the same > physical ACL data. In our case, we need to set a large number of files (and > directories) to the same ACL (content) - could we take any benefit from these > 'pseudo' referencing nature ? i.e. set ACL contents once and the job is done > ;-). It looks that mmputacl can only access the ACL data 'through' a filename > and not 'directly' - we just need the 'dirty' way ;-)" > > > Perhaps one could hack/patch that - but I can't recommend it. Would you > routinely hack/patch the GPFS metadata that comprises a directory? > Consider replicated and logged metadata ... Consider you've corrupted the > hash table of all ACL values... > > _______________________________________________ > gpfsug-discuss mailing list > gpfsug-discuss at gpfsug.org > http://gpfsug.org/mailman/listinfo/gpfsug-discuss _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at gpfsug.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
