<html><body><p><tt>Simon,</tt><br><br><tt>I spoke to a tester who worked on this line item. She thinks </tt><tt>mmchattr -E should have been documented. We will follow up. If it was an oversight it should be corrected soon.</tt><br><br><tt>Jamie</tt><br><br>Jamie Davis<br>GPFS Functional Verification Test (FVT)<br>jamiedavis@us.ibm.com<br><br><img width="16" height="16" src="cid:1__=0ABBF41BDFD7B1AF8f9e8a93df938690918c0AB@" border="0" alt="Inactive hide details for "Simon Thompson (Research Computing - IT Services)" ---19-07-2015 04:09:40 PM---On 19/07/2015 13:45, "><font color="#424282">"Simon Thompson (Research Computing - IT Services)" ---19-07-2015 04:09:40 PM---On 19/07/2015 13:45, "Frank Kraemer" <kraemerf@de.ibm.com> wrote: >>I was wondering if anyone had lo</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">"Simon Thompson (Research Computing - IT Services)" <S.J.Thompson@bham.ac.uk></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">gpfsug main discussion list <gpfsug-discuss@gpfsug.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">19-07-15 04:09 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [gpfsug-discuss] Immutable fileset features</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">gpfsug-discuss-bounces@gpfsug.org</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt><br><br>On 19/07/2015 13:45, "Frank Kraemer" <kraemerf@de.ibm.com> wrote:<br><br>>>I was wondering if anyone had looked at the immutable fileset features in<br>>4.1.1?<br>><br>>yes, Nils Haustein has see:<br>><br>></tt><tt><a href="https://www.ibm.com/developerworks/community/blogs/storageneers/entry/Insi">https://www.ibm.com/developerworks/community/blogs/storageneers/entry/Insi</a></tt><tt><br>>ght_to_the_IBM_Spectrum_Scale_GPFS_Immutability_function<br><br><br>I was re-reading some of this blog post and am a little confused.<br><br>It talks about setting retention times by setting the ATIME from touch, or<br>by using -E to mmchattr.<br><br>Does that mean if a file is accessed, then the ATIME is updated and so the<br>retention period is changed?<br><br>What if our retention policy is based on last access time of file +period<br>of time. I was thinking it would be useful to do a policy scan to find<br>newly access files and then set the retention (either directly by policy<br>if possible? Or by passing the file list to a script). Would this work or<br>if the ATIME is overloaded, then I guess we canšt use this?<br><br>Finally, is this a feature that is supported by IBM?<br><br>The -E flag for mmchattr is neither in the man page nor the online docs at:<br></tt><tt><a href="http://www-01.ibm.com/support/knowledgecenter/#!/STXKQY_4.1.1/com.ibm.spect">http://www-01.ibm.com/support/knowledgecenter/#!/STXKQY_4.1.1/com.ibm.spect</a></tt><tt><br>rum.scale.v4r11.adm.doc/bl1adm_mmchattr.htm<br><br>(My possibly incorrect understanding was that if its documented, then is<br>supported, otherwise it might work)?<br><br>Simon<br><br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at gpfsug.org<br></tt><tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></tt><tt><br><br></tt><br><BR>
</body></html>