Re: Deadlock on NFS server

[Francois Tigeot <ftigeot@xxxxxxxxxxxx>]

On Tue, Apr 06, 2010 at 10:35:37AM -0700, Matthew Dillon wrote:
> :
> :I just got a new sort of deadlock on a NFS server.
> :
> :During the extraction of a tarball archive by a FreeBSD client, the server
> :became unresponsive.
> :
> :It could still answer to pings but all other sort of network activity failed.
> :Ssh sessions were hanged, there was no answer to telnet commands, etc...
> :...
> :On the console there was a single message:
> :
> :	Warning, objcache(mbuf pkt hdr): Exhausted!
> 
>     How much memory does the server have?  What does 'netstat -m' say
>     on the server?

Actually, it is the same machine which had all sort of deadlock troubles with
the hammer cleanup code.

The main memory is 2GB.

# netstat -m
7/13312 mbufs in use (current/max):
469/6656 mbuf clusters in use (current/max)
257 mbufs and mbuf clusters allocated to data
6 mbufs and mbuf clusters allocated to packet headers
939 Kbytes allocated to network (5% of mb_map in use)
260 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines

The nfs service has not been really used since the last reboot. Should I try
to reproduct the deadlock conditions and monitor netstat -m output ?

-- 
Francois Tigeot