Thanks all, managed to rerun the policy with the additional list options (kb_allocated etc) and verified that indeed there are at least 60000 files with the same name that are 0 bytes, and more besides. Now my paranoia is setting in that somehow these files are all corrupted 😊 Cheers Richard From: gpfsug-discuss-bounces at spectrumscale.org [mailto:gpfsug-discuss-bounces at spectrumscale.org] On Behalf Of Sobey, Richard A Sent: 02 December 2017 18:53 To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org> Subject: Re: [gpfsug-discuss] Policy rule to list files based on access time Thank you all for your replies. I will take a look at them on Monday. And reply individually where I need to.. Richard Get Outlook for Android<https://aka.ms/ghei36> ________________________________ From: gpfsug-discuss-bounces at spectrumscale.org <gpfsug-discuss-bounces at spectrumscale.org> on behalf of Marc A Kaplan <makaplan at us.ibm.com> Sent: Saturday, December 2, 2017 6:03:25 PM To: gpfsug main discussion list Subject: Re: [gpfsug-discuss] Policy rule to list files based on access time You might want to look at FILE_SIZE. KB_ALLOCATED will be 0 if the file data fits into the inode. You might also want to use SIZE(FILE_SIZE) in the policy LIST rule, this will cause the KB_HIT and KB_CHOSEN numbers to be the sum of FILE_SIZEs instead of the default SIZE(KB_ALLOCATED). --marc of GPFS -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20171205/9593f4f0/attachment.html>