<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>Hi</p>
<p>while maybe not the solution to the exact problem, GPFS does
allow heat based tiering which seems to me like a more correct way
to ensure efficient utilisation of fast SSD space.<br>
<br>
<a moz-do-not-send="true" href="https://www.ibm.com/docs/en/storage-scale/5.0.5?topic=scale-file-heat-tracking-file-access-temperature" class="moz-txt-link-freetext">https://www.ibm.com/docs/en/storage-scale/5.0.5?topic=scale-file-heat-tracking-file-access-temperature</a></p>
<p>Best,<br>
</p>
<pre class="moz-signature" cols="72">Ott Oopkaup
University of Tartu, High Performance Computing Centre
Systems Administrator</pre>
<div class="moz-cite-prefix">On 6/29/23 12:01, Alec wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAGhSTwhhKnowntKD9fLVBKW-wsnfRvFmCEbkCwuw-cTLNf-ApA@mail.gmail.com">
<div dir="ltr">Yeah that kind of placement isn't possible, because
you can only use attributes you know at the time of inode
creation. When a file is created it's created with the current
timestamp and then updated (usually after the copy finishes).
If the majority of your data is going to be older than 365 days
you may want to make your file placement default to your pool2,
and then when you've finished copying all your older data, and
want to freshen your data, update the placement policy it to the
proper pool so new data hits the high speed disk.
<div><br>
</div>
<div>You can use a file path/name in the placement policy and
some copy engines do give inodes temporary names before giving
them their proper name... like rsync will start a file off
with a . (and add a random suffix) until the file is
completely transferred, then move it to the destination
filename, then it will update the date, time, and ownership on
that inode. So you could have your placement engine put
anything starting with a . into your pool2 and then migrate
fresher files back up to your higher tiered storage if
desired.</div>
<div><br>
</div>
<div>Not sure if any of that helps.</div>
<div><br>
</div>
<div>Alec</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Jun 28, 2023 at
10:12 PM Timm Stamer <<a href="mailto:timm.stamer@uni-oldenburg.de" moz-do-not-send="true" class="moz-txt-link-freetext">timm.stamer@uni-oldenburg.de</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello
Prasad,<br>
<br>
we use this in our weekly policy run:<br>
<br>
RULE 'migrate cold data' MIGRATE FROM POOL 'system' TO POOL
'data'<br>
WHERE CURRENT_TIMESTAMP - ACCESS_TIME > INTERVAL '30' DAYS<br>
<br>
<br>
I do not know if a direct placement based on timestamps is
possible.<br>
<br>
<br>
<br>
Kind regards<br>
Timm Stamer<br>
<br>
<br>
Am Mittwoch, dem 28.06.2023 um 23:18 +0000 schrieb Prasad
Surampudi:<br>
> <br>
> <br>
> <br>
> ACHTUNG! Diese E-Mail kommt von Extern!WARNING! This
email originated<br>
> off-campus.<br>
> <br>
> <br>
> <br>
> <br>
> Can we setup a file placement policy based on creating
and<br>
> modification times when copying data from Windows into
GPFS? It looks<br>
> like the placement policy only accepts only CREATION_TIME
and not<br>
> MODIFICATION_TIME or ACCESS_TIME. If I try to use these,
I get<br>
> message saying these are not supported in the context
(placement?)<br>
> But even the policy with CREATION_TIME is not working
properly. We<br>
> wanted files with CREATION_TIME which is 365 days ago go
to a<br>
> different pool other than ‘system’. But when we copy
files it is<br>
> dumping all files into system pool. But the creation time
is looks<br>
> correct on the file after copied into GPFS. Does it check
file<br>
> CREATION_TIME when a file gets copied over to GPFS?<br>
> <br>
> Here is the placement policy:<br>
> RULE ‘tiering’ SET POOL ‘pool2’<br>
> WHERE ( DAYS(CURRENT_TIMESTAMP) - DAYS(CREATION_TIME)
> 365 )<br>
> RULE ‘default’ SET POOL ‘system’<br>
> <br>
> <br>
> <br>
> Logo<br>
> <br>
> Description automatically generated<br>
> <br>
> Prasad Surampudi | Sr. Systems Engineer<br>
> <a href="mailto:prasad.surampudi@theatsgroup.com" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">prasad.surampudi@theatsgroup.com</a> |
302.419.5833 <br>
> <br>
> Innovative IT consulting & modern
infrastructure solutions<br>
> <a href="http://www.theatsgroup.com" rel="noreferrer" target="_blank" moz-do-not-send="true">www.theatsgroup.com</a><br>
> _______________________________________________<br>
> gpfsug-discuss mailing list<br>
> gpfsug-discuss at <a href="http://gpfsug.org" rel="noreferrer" target="_blank" moz-do-not-send="true">gpfsug.org</a><br>
> <a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org" rel="noreferrer" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org</a><br>
_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at <a href="http://gpfsug.org" rel="noreferrer" target="_blank" moz-do-not-send="true">gpfsug.org</a><br>
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org" rel="noreferrer" target="_blank" moz-do-not-send="true" class="moz-txt-link-freetext">http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org</a><br>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at gpfsug.org
<a class="moz-txt-link-freetext" href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org">http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org</a>
</pre>
</blockquote>
</body>
</html>