High rate of authrefrsh calls when no NFS activity is required

High rate of authrefrsh calls when no NFS activity is required

[Ulrich Gemkow]

Hello,

we see a high number of authrefrsh calls (about 1000/s) while
IMHO no NFS activity is required.

More details: We have an archive server which is booted from
a ram disc and mounts his system files (/usr, /lib, ...) per
NFS v3 (mounted with the option nolock).

When the archive server dumps its local data to tape he
generates about 1000 authrefrsh calls per second despite the
fact that it does not need any data from the nfs server. There
is a correponding high number of getattr calls but no read/write
over NFS. The archive server has some files open over NFS
(i.e. the dump utility), but these are readonly.

My questions:

- Is there any way to see for which files the getattr calls
  are made? This would help to debug the problem. Is there
  any other means to see what the client wants from the
  NFS server?

- Can anyone explain where these authrefrsh calls come from?
  They result in a severe performance degration during the 
  dump to tape

Thank you and best regards

-Ulrich

-- 
|-----------------------------------------------------------------------
| Ulrich Gemkow
| University of Stuttgart
| Institute of Communication Networks and Computer Engineering (IKR)
|-----------------------------------------------------------------------