Thanks Fred. A
________________________________ From: [email protected] [[email protected]] on behalf of Frederick Stock [[email protected]] Sent: Tuesday, March 19, 2019 12:29 PM To: [email protected] Cc: [email protected] Subject: Re: [gpfsug-discuss] Calculate evicted space with a policy You can scan for files using the MISC_ATTRIBUTES and look for those that are not cached, that is without the 'u' setting, and track their file size. I think that should work. Fred __________________________________________________ Fred Stock | IBM Pittsburgh Lab | 720-430-8821 [email protected] ----- Original message ----- From: "Dorigo Alvise (PSI)" <[email protected]> Sent by: [email protected] To: "[email protected]" <[email protected]> Cc: Subject: [gpfsug-discuss] Calculate evicted space with a policy Date: Tue, Mar 19, 2019 5:27 AM Dear users, is there a way (through a policy) to list the files (and their size) that are actually completely evicted by AFM from the cache filesystem ? I used a policy with the clause KB_ALLOCATED=0, but it is clearly not precise, because it also includes files that are not evicted, but are so small that they fit into their inodes (I'm assuming that GPFS inode structure has this feature similar to some regular filesystems, like ext4... otherwise I could not explain some non empty file with 0 allocated KB that have been fetched, i.e. non-evicted). Many thanks, Alvise _______________________________________________ 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
