got today messages on my netapp 3020c:
[filer: nfsd.assist.queue.exceeding.limit:warning] javascript:popEMS('nfsd.assist.queue.exceeding.limit');: There are 132 items on the NFS assist queue, which exceeds the cutoff limit of 130.
found nothing in my handbooks, and syslog-translator does not know what this would be. at the same time we had some severe performance-problems, but we dont know yet, if these were triggered by that message.
is there something i could do?
yours josef radinger it-services medical university innsbruck
There is a limited number of nfs messages available on any system based on some formula netapp uses to balance memory allocation for OS subsystems. The nfsd.assist queue is where each nfs call handles things like authentication, and name translation. Normally this is very quick and the nfs message holder is returned to the pool for reuse. In some cases, like yours, the queue has used up all the available messages. this could be becasue your system is very busy, or it could be that it's having name server problems, or something else.
You can do an nfs_history on the 3020 and see if it's taking a long time to make responses, and an nfsstat -d to see if there are any appearant errors going on. I'd look for any kind of physical problems (network, etc) first, then I'd look at performance being a bottle neck. There's nothing you can do to increase the number of nfs messages, short of adding more memory to the box.
hope that helps.
Mike
On Thu, 16 Feb 2006, josef radinger Said:
got today messages on my netapp 3020c:
[filer: nfsd.assist.queue.exceeding.limit:warning] javascript:popEMS('nfsd.assist.queue.exceeding.limit');: There are 132 items on the NFS assist queue, which exceeds the cutoff limit of 130.
found nothing in my handbooks, and syslog-translator does not know what this would be. at the same time we had some severe performance-problems, but we dont know yet, if these were triggered by that message.
is there something i could do?
yours josef radinger it-services medical university innsbruck
The acutal command is in priv set advanced mode, and it's nfs_hist. You can use nfs_hist -z to zero the stats, and take samplings over time to see trending in responce latencys.
-Blake
On 2/16/06, Mike Cutler mikec@pdi.com wrote:
There is a limited number of nfs messages available on any system based on some formula netapp uses to balance memory allocation for OS subsystems. The nfsd.assist queue is where each nfs call handles things like authentication, and name translation. Normally this is very quick and the nfs message holder is returned to the pool for reuse. In some cases, like yours, the queue has used up all the available messages. this could be becasue your system is very busy, or it could be that it's having name server problems, or something else.
You can do an nfs_history on the 3020 and see if it's taking a long time to make responses, and an nfsstat -d to see if there are any appearant errors going on. I'd look for any kind of physical problems (network, etc) first, then I'd look at performance being a bottle neck. There's nothing you can do to increase the number of nfs messages, short of adding more memory to the box.
hope that helps.
Mike
On Thu, 16 Feb 2006, josef radinger Said:
got today messages on my netapp 3020c:
[filer: nfsd.assist.queue.exceeding.limit:warning] javascript:popEMS('nfsd.assist.queue.exceeding.limit');: There are 132 items on the NFS assist queue, which exceeds the cutoff limit of 130.
found nothing in my handbooks, and syslog-translator does not know what this would be. at the same time we had some severe performance-problems, but we dont know yet, if these were triggered by that message.
is there something i could do?
yours josef radinger it-services medical university innsbruck
-- Mike Cutler - mikec@pdi.com PDI/Dreamworks Animation Technology
What release are you running? I think an answer maybe found though examining nfsstat -d. Can you send that output to us?
-Blake
On 2/16/06, josef radinger josef.radinger@i-med.ac.at wrote:
got today messages on my netapp 3020c:
[filer: nfsd.assist.queue.exceeding.limit:warning] javascript:popEMS('nfsd.assist.queue.exceeding.limit');: There are 132 items on the NFS assist queue, which exceeds the cutoff limit of 130.
found nothing in my handbooks, and syslog-translator does not know what this would be. at the same time we had some severe performance-problems, but we dont know yet, if these were triggered by that message.
is there something i could do?
yours josef radinger it-services medical university innsbruck
seems that we had dns-problems, will create some sort of /etc/hosts file to be somewhat independant to our dns. ... access cache name service errors causing not caches (ro/rw, root) = (6995, 76006 ) ...
thanks josef
ps.: we run 7.0.3
On Thu, 2006-02-16 at 08:43 -0800, Blake Golliher wrote:
What release are you running? I think an answer maybe found though examining nfsstat -d. Can you send that output to us?
-Blake
On 2/16/06, josef radinger josef.radinger@i-med.ac.at wrote:
got today messages on my netapp 3020c:
[filer: nfsd.assist.queue.exceeding.limit:warning] javascript:popEMS('nfsd.assist.queue.exceeding.limit');: There are 132 items on the NFS assist queue, which exceeds the cutoff limit of 130.
found nothing in my handbooks, and syslog-translator does not know what this would be. at the same time we had some severe performance-problems, but we dont know yet, if these were triggered by that message.
is there something i could do?
yours josef radinger it-services medical university innsbruck
-
Blake Golliher -
josef radinger -
Josef Radinger
-
Mike Cutler