Subject: Re: nfsd lockups with xfs during SPEC SFS testing
From: Steve Lord <lord@sgi.com>
To: "HABBINGA,ERIK   ""(HP-Loveland,ex1)" <erik_habbinga@hp.com>
Cc: "'linux-xfs@oss.sgi.com'" <linux-xfs@oss.sgi.com>
In-Reply-To: <F341E03C8ED6D311805E00902761278C0C35DD12@xfc04.fc.hp.com>
References: <F341E03C8ED6D311805E00902761278C0C35DD12@xfc04.fc.hp.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 31 Jan 2002 16:16:05 -0600
Message-Id: <1012515365.26363.274.camel@jen.americas.sgi.com>
Mime-Version: 1.0
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk
Status: O
Content-Length: 1159
Lines: 31

On Thu, 2002-01-31 at 11:59, HABBINGA,ERIK (HP-Loveland,ex1) wrote:
> I'm running linux 2.4.17 with a version of XFS downloaded via CVS on Jan
> 30th.  When I run the SPEC SFS NFS test against this kernel, nfsd stops
> responding after awhile.  I captured the state of all of the system
> processes via magic sysrq, and found 24 nfsd processes locked up in various
> stages of the nfsd_lookup code:
> 
> - 20 of them were locked up in the fh_lock call before lookup_one_len in
> nfsd_lookup().  
> - 2 processes were locked up in the _pagebuf_grab_lock call inside
> _pagebuf_find_lockable_buffer().
> - 2 processes were locked up in the pagebuf_iowait() call in
> pagebuf_iostart()
> 
> Any ideas on what may be wrong, and how I can help debug and solve this
> problem?  I've attached the call traces for the locked up nfsd processes.  I
> can provide vmlinux and System.map for this kernel to help debugging.

Is this a regression, i.e. did it used to work? And can you say when on
the 30th?

Thanks

   Steve


-- 

Steve Lord                                      voice: +1-651-683-3511
Principal Engineer, Filesystem Software         email: lord@sgi.com