Rob Leitman <robl@xxxxxxxxxxxx> wrote: > Cookies: idx=4 dat=15 spc=0 > ... > Invals : n=17536803 run=0 That looks really weird. You've got 15 data files which are being invalidated over 17 million times between them - but in no cases do you have any invalidation states reached. (Indices may not be invalidated). > Objects: alc=0 nal=0 avl=0 ded=0 There are no objects allocated. Do you have a cache actually attached? Anyway, the fscache_n_invalidates counter counts calls to __fscache_invalidate() - which should only be called through fscache_invalidate(). That in turn is called from nfs_fscache_invalidate() which is called in two places: (1) nfs_set_cache_invalid() - if NFS decides to invalidate the data. (2) update_changeattr() - if NFSv4 sees an altered change attribute. Can you use wireshark to check that the change attribute is remaining constant? David -- Linux-cachefs mailing list Linux-cachefs@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cachefs
