<html><body><p>Hi Luke,<br><br>Cache eviction simply frees up space in the cache, but the inode/file is always the same. It does not delete and recreate the file in the cache. This is why you can continue to view files in the cache namespace even if they are evicted.<br><br>Dean Hildebrand<br>IBM Almaden Research Center<br><br><br><img width="16" height="16" src="cid:1__=07BBF5F6DFF47B548f9e8a93df938690918c07B@" border="0" alt="Inactive hide details for Luke Raimbach ---02/26/2016 02:52:52 AM---Hi Dean, Thanks for this – I had hoped this was the case. "><font color="#424282">Luke Raimbach ---02/26/2016 02:52:52 AM---Hi Dean, Thanks for this – I had hoped this was the case. However what I’m now wondering is, if we o</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Luke Raimbach <Luke.Raimbach@crick.ac.uk></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">gpfsug main discussion list <gpfsug-discuss@spectrumscale.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">02/26/2016 02:52 AM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [gpfsug-discuss] AFM and Placement Policies</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font color="#1F497D" face="Calibri">Hi Dean,</font><br><font color="#1F497D" face="Calibri"> </font><br><font color="#1F497D" face="Calibri">Thanks for this – I had hoped this was the case. However what I’m now wondering is, if we operate the cache in independent-writer mode and the new file was pushed back home (conforming to cache, then home placement policies), then is subsequently evicted from the cache; if it needs to be pulled back for local operations in the cache, will the cache cluster see this file as “new” for the third time?</font><br><font color="#1F497D" face="Calibri"> </font><br><font color="#1F497D" face="Calibri">Cheers,</font><br><font color="#1F497D" face="Calibri">Luke.</font><br><a name="_MailEndCompose"></a><font color="#1F497D" face="Calibri"> </font><br><b><font face="Calibri">From:</font></b><font face="Calibri"> gpfsug-discuss-bounces@spectrumscale.org [</font><font face="Calibri"><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org">mailto:gpfsug-discuss-bounces@spectrumscale.org</a></font><font face="Calibri">] </font><b><font face="Calibri">On Behalf Of </font></b><font face="Calibri">Dean Hildebrand</font><b><font face="Calibri"><br>Sent:</font></b><font face="Calibri"> 24 February 2016 19:17</font><b><font face="Calibri"><br>To:</font></b><font face="Calibri"> gpfsug main discussion list <gpfsug-discuss@spectrumscale.org></font><b><font face="Calibri"><br>Cc:</font></b><font face="Calibri"> gpfsug main discussion list <gpfsug-discuss@gpfsug.org></font><b><font face="Calibri"><br>Subject:</font></b><font face="Calibri"> Re: [gpfsug-discuss] AFM and Placement Policies</font><br><font size="4" face="Times New Roman"> </font><p><font size="4" face="Times New Roman">Hi Luke,<br><br>The short answer is yes, when the file is created on the home, it is a 'brand new' creation that will conform to any and all new placement policies that you set on the home site. So if you are using NFS in the relationship, then it is simply created just like any other file is created over NFS. The same goes when using GPFS to the home cluster...<br><br>Dean<br>IBM Almaden Research Center<br><br><br></font><img src="cid:1__=07BBF5F6DFF47B548f9e8a93df938690918c07B@" width="16" height="16" alt="Inactive hide details for Luke Raimbach ---02/24/2016 06:05:43 AM---Hi All, I have two GPFS file systems (A and B) and an AFM S"><font size="4" color="#424282" face="Times New Roman">Luke Raimbach ---02/24/2016 06:05:43 AM---Hi All, I have two GPFS file systems (A and B) and an AFM Single Writer relationship: /fsB/cache wri</font><font size="4" face="Times New Roman"><br></font><font color="#5F5F5F" face="Times New Roman"><br>From: </font><font face="Times New Roman">Luke Raimbach <</font><a href="mailto:Luke.Raimbach@crick.ac.uk"><u><font color="#0000FF" face="Times New Roman">Luke.Raimbach@crick.ac.uk</font></u></a><font face="Times New Roman">></font><font color="#5F5F5F" face="Times New Roman"><br>To: </font><font face="Times New Roman">gpfsug main discussion list <</font><a href="mailto:gpfsug-discuss@gpfsug.org"><u><font color="#0000FF" face="Times New Roman">gpfsug-discuss@gpfsug.org</font></u></a><font face="Times New Roman">></font><font color="#5F5F5F" face="Times New Roman"><br>Date: </font><font face="Times New Roman">02/24/2016 06:05 AM</font><font color="#5F5F5F" face="Times New Roman"><br>Subject: </font><font face="Times New Roman">[gpfsug-discuss] AFM and Placement Policies</font><font color="#5F5F5F" face="Times New Roman"><br>Sent by: </font><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org"><u><font color="#0000FF" face="Times New Roman">gpfsug-discuss-bounces@spectrumscale.org</font></u></a><br><hr width="100%" size="2" align="left" noshade><br><font size="4" face="Times New Roman"><br><br></font><font face="Courier New"><br>Hi All,<br><br>I have two GPFS file systems (A and B) and an AFM Single Writer relationship: /fsB/cache writes back to /fsA/home<br><br>I have a placement policy which sets extended attributes on file creation in /fsB/cache.<br><br>When I create a new file in /fsB/cache/new.file and it is pushed back by AFM to /fsA/home/new.file, can the home fileset apply a different placement policy to add or modify extended attributes? I guess the deeper question is does each file system in this arrangement see the new.file as "new" in both locations?<br><br>Cheers,<br>Luke.<br><br>Luke Raimbach</font><font face="Cambria Math"></font><font face="Courier New"><br>Senior HPC Data and Storage Systems Engineer,<br>The Francis Crick Institute,<br>Gibbs Building,<br>215 Euston Road,<br>London NW1 2BE.<br><br>E: </font><a href="mailto:luke.raimbach@crick.ac.uk"><u><font color="#0000FF" face="Courier New">luke.raimbach@crick.ac.uk</font></u></a><font face="Courier New"><br>W: </font><a href="http://www.crick.ac.uk/"><u><font color="#0000FF" face="Courier New">www.crick.ac.uk</font></u></a><font face="Courier New"><br><br>The Francis Crick Institute Limited is a registered charity in England and Wales no. 1140062 and a company registered in England and Wales no. 06885462, with its registered office at 215 Euston Road, London NW1 2BE.<br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org</font><u><font color="#0000FF" face="Courier New"><br></font></u><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><u><font color="#0000FF" face="Courier New">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></u></a><font size="4" face="Times New Roman"><br><br></font><p><i><font color="#707173" face="Trebuchet MS">The Francis Crick Institute Limited is a registered charity in England and Wales no. 1140062 and a company registered in England and Wales no. 06885462, with its registered office at 215 Euston Road, London NW1 2BE. </font></i><tt>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></tt><tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></tt><tt><br></tt><p><p><BR>
</body></html>