[OpenAFS] Re: OpenAFS client cache overrun?

Andrew Deason adeason@sinenomine.net
Fri, 7 Mar 2014 15:51:23 -0600

On Fri, 07 Mar 2014 13:51:06 -0500
Eric Chris Garrison <ecgarris@iu.edu> wrote:

> I'll have to look for that message from Andrew to gather data if the
> problem crops up again.

It's this message:


The easiest / most basic information to get is just the stack trace from
the daemon that is supposed to be trimming the cache back when it gets
full. That message contains the commands where you can get that
information via the 'crash' tool.

Or, another way to get that information is by running this:

# echo t > /proc/sysrq-trigger

That will generate a ton of information to the kernel log, which you'd
need to sift through or give to someone else. But it's at least a lot
easier to set up and run.

> Thanks also for the mention of AFS cache bypass, I think that may be a
> BIG help with this problem.

'Cache bypass' I don't believe is considered the most stable of
features. It could indeed maybe help here, but I'd be looking out for
kernel panics.

Andrew Deason