<font size=2 face="sans-serif">AFM cannot keep directory mtime in sync.
Directory mtime changes during readdir when files are created inside it
after initial lookup. This is a known limitation today.</font><br><br><font size=2 face="sans-serif">~Venkat (vpuvvada@in.ibm.com)</font><br><br><br><br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif"><Paul.Tomlinson@awe.co.uk></font><br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif"><gpfsug-discuss@spectrumscale.org></font><br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">01/09/2017 09:30 PM</font><br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [gpfsug-discuss]
AFM Migration Issue</font><br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">gpfsug-discuss-bounces@spectrumscale.org</font><br><hr noshade><br><br><br><tt><font size=2>Hi,<br><br>We have already come across the issues you have seen below, and worked
around them.<br><br>If you run the pre-fetch with just the --meta-data-only, then all the date
stamps are correct for the dirs., as soon as you run --list-only all the
directory times change to now.<br><br>We have tried rsync but this did not appear to work.<br><br><br>-----Original Message-----<br>From: gpfsug-discuss-bounces@spectrumscale.org [</font></tt><a href="mailto:gpfsug-discuss-bounces@spectrumscale.org"><tt><font size=2>mailto:gpfsug-discuss-bounces@spectrumscale.org</font></tt></a><tt><font size=2>]
On Behalf Of Peter Childs<br>Sent: 09 January 2017 15:49<br>To: gpfsug-discuss@spectrumscale.org<br>Subject: EXTERNAL: Re: [gpfsug-discuss] AFM Migration Issue<br><br>Interesting, I'm currently doing similar but currently am only using read-only
to premigrate the filesets, The directory file stamps don't agree
with the original but neither are they all marked when they were migrated.
So there is something very weird going on..... (We're planning to switch
them to Local Update when we move the users over to them)<br><br>We're using a mmapplypolicy on our old gpfs cluster to get the files to
migrate, and have noticed that you need a<br><br>RULE EXTERNAL LIST ESCAPE '%/'<br><br>line otherwise files with % in the filenames don't get migrated and through
errors.<br><br>I'm trying to work out if empty directories or those containing only empty
directories get migrated correctly as you can't list them in the mmafmctl
prefetch statement. (If you try (using DIRECTORIES_PLUS) they through errors)<br><br>I am very interested in the solution to this issue.<br><br>Peter Childs<br>Queen Mary, University of London<br><br><br>________________________________________<br>From: gpfsug-discuss-bounces@spectrumscale.org <gpfsug-discuss-bounces@spectrumscale.org>
on behalf of Paul.Tomlinson@awe.co.uk <Paul.Tomlinson@awe.co.uk><br>Sent: Monday, January 9, 2017 3:09:43 PM<br>To: gpfsug-discuss@spectrumscale.org<br>Subject: [gpfsug-discuss] AFM Migration Issue<br><br>Hi All,<br><br>We have just completed the first data move from our old cluster to the
new one using AFM Local Update as per the guide, however we have noticed
that all date stamps on the directories have the date they were created
on(e.g. 9th Jan 2017) , not the date from the old system (e.g. 14th April
2007), whereas all the files have the correct dates.<br><br>Has anyone else seen this issue as we now have to convert all the directory
dates to their original dates !<br><br><br><br><br>The information in this email and in any attachment(s) is commercial in
confidence. If you are not the named addressee(s) or if you receive this
email in error then any distribution, copying or use of this communication
or the information in it is strictly prohibited. Please notify us immediately
by email at admin.internet(at)awe.co.uk, and then delete this message from
your computer. While attachments are virus checked, AWE plc does not accept
any liability in respect of any virus which is not detected.<br><br>AWE Plc<br>Registered in England and Wales<br>Registration No 02763902<br>AWE, Aldermaston, Reading, RG7 4PR<br><br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><font size=2>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size=2><br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><font size=2>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size=2><br><br><br><br>The information in this email and in any attachment(s) is <br>commercial in confidence. If you are not the named addressee(s) <br>or <br>if you receive this email in error then any distribution, copying or <br>use of this communication or the information in it is strictly <br>prohibited. Please notify us immediately by email at <br>admin.internet(at)awe.co.uk, and then delete this message from <br>your computer. While attachments are virus checked, AWE plc <br>does not accept any liability in respect of any virus which is not <br>detected.<br><br>AWE Plc<br>Registered in England and Wales<br>Registration No 02763902<br>AWE, Aldermaston, Reading, RG7 4PR<br><br>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at spectrumscale.org<br></font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><font size=2>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size=2><br><br></font></tt><br><br><BR>