[gpfsug-discuss] mmapplypolicy on nested filesets ...
Marc A Kaplan
makaplan at us.ibm.com
Wed Apr 18 19:00:13 BST 2018
I suggest you remove any FOR FILESET(...) specifications from your rules
and then run
mmapplypolicy
/path/to/the/root/directory/of/the/independent-fileset-you-wish-to-scan
... --scope inodespace -P your-policy-rules-file ...
See also the (RTFineM) for the --scope option and the Directory argument
of the mmapplypolicy command.
That is the best, most efficient way to scan all the files that are in a
particular inode-space. Also, you must have all filesets of interest
"linked" and the file system must be mounted.
Notice that "independent" means that the fileset name is used to denote
both a fileset and an inode-space, where said inode-space contains the
fileset of that name and possibly other "dependent" filesets...
IF one wished to search the entire file system for files within several
different filesets, one could use rules with
FOR FILESET('fileset1','fileset2','and-so-on')
Or even more flexibly
WHERE FILESET_NAME LIKE 'sql-like-pattern-with-%s-and-maybe-_s'
Or even more powerfully
WHERE regex(FILESET_NAME, 'extended-regular-.*-expression')
From: "Jaime Pinto" <pinto at scinet.utoronto.ca>
To: "gpfsug main discussion list" <gpfsug-discuss at spectrumscale.org>
Date: 04/18/2018 01:00 PM
Subject: [gpfsug-discuss] mmapplypolicy on nested filesets ...
Sent by: gpfsug-discuss-bounces at spectrumscale.org
A few months ago I asked about limits and dynamics of traversing
depended .vs independent filesets on this forum. I used the
information provided to make decisions and setup our new DSS based
gpfs storage system. Now I have a problem I couldn't' yet figure out
how to make it work:
'project' and 'scratch' are top *independent* filesets of the same
file system.
'proj1', 'proj2' are dependent filesets nested under 'project'
'scra1', 'scra2' are dependent filesets nested under 'scratch'
I would like to run a purging policy on all contents under 'scratch'
(which includes 'scra1', 'scra2'), and TSM backup policies on all
contents under 'project' (which includes 'proj1', 'proj2').
HOWEVER:
When I run the purging policy on the whole gpfs device (with both
'project' and 'scratch' filesets)
* if I use FOR FILESET('scratch') on the list rules, the 'scra1' and
'scra2' filesets under scratch are excluded (totally unexpected)
* if I use FOR FILESET('scra1') I get error that scra1 is dependent
fileset (Ok, that is expected)
* if I use /*FOR FILESET('scratch')*/, all contents under 'project',
'proj1', 'proj2' are traversed as well, and I don't want that (it
takes too much time)
* if I use /*FOR FILESET('scratch')*/, and instead of the whole device
I apply the policy to the /scratch mount point only, the policy still
traverses all the content of 'project', 'proj1', 'proj2', which I
don't want. (again, totally unexpected)
QUESTION:
How can I craft the syntax of the mmapplypolicy in combination with
the RULE filters, so that I can traverse all the contents under the
'scratch' independent fileset, including the nested dependent filesets
'scra1','scra2', and NOT traverse the other independent filesets at
all (since this takes too much time)?
Thanks
Jaime
PS: FOR FILESET('scra*') does not work.
************************************
TELL US ABOUT YOUR SUCCESS STORIES
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.scinethpc.ca_testimonials&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=cvpnBBH0j41aQy0RPiG2xRL_M8mTc1izuQD3_PmtjZ8&m=y0aRzkzp0QA9QR8eh3XtN6PETqWYDCNvItdihzdueTE&s=IpwHlr0YNr7rgV7gI8Y2sxIELLIwA15KK4nBnv9BYWk&e=
************************************
---
Jaime Pinto - Storage Analyst
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
https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=cvpnBBH0j41aQy0RPiG2xRL_M8mTc1izuQD3_PmtjZ8&m=y0aRzkzp0QA9QR8eh3XtN6PETqWYDCNvItdihzdueTE&s=aff0vMJkKd-Z3pw3-jckmI3ejqXh8aSr8rxkKf3OGdk&e=
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20180418/4c2f3a86/attachment-0002.htm>
More information about the gpfsug-discuss
mailing list