[EMAIL PROTECTED] (Chris Cowan) writes:
> Does anyone have a util to gather statistics on cache consumption vs.
> filepath? I have heard rumblings of a kdump util at CMU, but don't
> know if it really fits the bill.
kdump is/will be a kerberos authenticated version of rdump. Nothing to
do with this kind of thing.
> I have a customer that is exhausting
> his cache and wants to try and determine what is causing it.
I'm not sure I understand how you can "exhaust" the cache. Do you mean
perhaps that it is turning over quickly and not much is sticking in it?
A first pass look at the contents is fairly easy to do with cmdebug.
Call it like "cmdebug localhost -long" and it is mostly self
explanatory. You get bunches of entries like
** Cache entry @ 0xfb0a6b18 for 1.251658492.2772.194600
19 bytes DV 1 refcnt 0
callback 80020a19 expires 743479628
0 opens 0 writers
mount point
states (0x1), stat'd
The second number in the 4-tuple is the volume id. You could count
those to see usage by volume. Using this and the file size info, you
should be able to get somewhere.
dan
cmu comp services
[EMAIL PROTECTED]
