| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 20 Oct 2011 12:37:05 -0700 From: Mark Moseley <moseleymark@...il.com> To: David Howells <dhowells@...hat.com> Cc: Linux filesystem caching discussion list <linux-cachefs@...hat.com>, linux-kernel@...r.kernel.org Subject: Re: [Linux-cachefs] 3.0.3 64-bit Crash running fscache/cachefilesd On Thu, Oct 20, 2011 at 1:46 AM, David Howells <dhowells@...hat.com> wrote: > Mark Moseley <moseleymark@...il.com> wrote: > >> I left the existing cache in place. For a few hours, it was culling > > That will be whilst the inode cache was filling, I suspect. > >> Is there anything I can do to verify whether the objects are indeed >> pinned? This is a pretty busy box. The nfs inode cache is quite large >> (from slabtop): > > Hmmm... Can you get me a dump of /proc/fs/fscache/stats to look at? > > The "Objects:" and "Relinqs:" lines are the most interesting. On the first > line avl=N shows the number of objects that are in the "available" state - > ie. are live for caching. > > Also, can you do: > > df -i /path/to/cache/partition > > to get the number of inodes available and used. # df /var/cache/fscache/ Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdb6 29338652 16148968 11699352 58% /var/cache/fscache # df -i /var/cache/fscache/ Filesystem Inodes IUsed IFree IUse% Mounted on /dev/sdb6 1864128 339163 1524965 19% /var/cache/fscache -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists