I think you have the sign wrong on your weight. A simple way of ordering the files oldest first is
WEIGHT(DAYS(CURRENT_TIMESTAMP) - DAYS(ACCESS_TIME)) adding 100,000 does nothing to change the order. WEIGHT can be any numeric SQL expression. So come to think of it WEIGHT( - DAYS(ACCESS_TIME) ) is even simpler and will yield the same ordering Also, you must run or schedule the mmapplypolicy command to run to actually do the migration. It doesn't happen until the mmapplypolicy command is running. You can run mmapplypolicy periodically (e.g. with crontab) or on demand with mmaddcallback (GPFS events facility) This is all covered in the very fine official Spectrum Scale documentation and/or some of the supplemental IBM red books, all available for free downloads from ibm.com --marc of GPFS From: Stef Coene <stef.co...@docum.org> To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org> Date: 02/27/2017 08:55 AM Subject: [gpfsug-discuss] Policy question Sent by: gpfsug-discuss-boun...@spectrumscale.org Hi, I have a file system with 2 pools: V500001 and NAS01. I want to use pool V500001 as the default and migrate the oldest files to the pool NAS01 when the pool V500001 fills up. Whatever rule combination I tried, I can not get this working. This is the currently defined policy (created by the GUI): RULE 'Migration' MIGRATE FROM POOL 'V500001' THRESHOLD(95,85) WEIGHT(100000 - DAYS(CURRENT_TIMESTAMP) - DAYS(ACCESS_TIME)) TO POOL 'NAS01' RULE 'Default to V5000' SET POOL 'V500001' And also, how can I monitor the migration processes? Stef _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss