[gpfsug-discuss] Inode reuse on AFM cache eviction

[Venkateswara R Puvvada]

Hi,

AFM does not support inode eviction, only data blocks are evicted and the 
file's metadata will remain in the fileset.

~Venkat (vpuvvada at in.ibm.com)



From:   Andreas Mattsson <andreas.mattsson at maxiv.lu.se>
To:     GPFS User Group <gpfsug-discuss at spectrumscale.org>
Date:   09/05/2019 03:39 PM
Subject:        [EXTERNAL] [gpfsug-discuss] Inode reuse on AFM cache 
eviction
Sent by:        gpfsug-discuss-bounces at spectrumscale.org



Hi,
Does anyone here know if cache eviction on a AFM cache also make the 
inodes used by the evicted files available for reuse?
Basically, I'm trying to figure out if it is enough to have sufficient 
inode space in my cache filesets to keep the maximum expected 
simultaneously cached files, or if I need the same inode space as for the 
total amount of files that will reside in the home of the cache. 

Regards,
Andreas Mattsson

____________________________________________


Andreas Mattsson
Systems Engineer
 
MAX IV Laboratory
Lund University
P.O. Box 118, SE-221 00 Lund, Sweden
Visiting address: Fotongatan 2, 224 84 Lund
Mobile: +46 706 64 95 44
andreas.mattsson at maxiv.lu.se
www.maxiv.se
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=92LOlNh2yLzrrGTDA7HnfF8LFr55zGxghLZtvZcZD7A&m=5omqUvEiiIKUhShJOBEgb3WwLU5uy-8o_4--y0TOuw0&s=ZFAcjvG5LrsnsCJgIf9f1320V866HKG6iJGteRQ7oac&e= 





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20190905/c2373088/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 4232 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20190905/c2373088/attachment-0002.png>