From owner-freebsd-fs@FreeBSD.ORG  Tue Jan 11 12:46:45 2005
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B7E1816A4CE
	for <freebsd-fs@freebsd.org>; Tue, 11 Jan 2005 12:46:45 +0000 (GMT)
Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net
	[194.217.242.92])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6313643D41
	for <freebsd-fs@freebsd.org>; Tue, 11 Jan 2005 12:46:45 +0000 (GMT)
	(envelope-from simon_freebsd_fs@bigblue.demon.co.uk)
Received: from demon-gw.ledwoodtechnology.co.uk ([80.177.235.49]
	helo=[192.168.25.19])
	by anchor-post-34.mail.demon.net with esmtp (Exim 4.42)
	id 1CoLQ4-000Oz4-Dt
	for freebsd-fs@freebsd.org; Tue, 11 Jan 2005 12:46:44 +0000
Message-ID: <41E3CAB4.5000009@bigblue.demon.co.uk>
Date: Tue, 11 Jan 2005 12:46:44 +0000
From: Simon Truss <simon_freebsd_fs@bigblue.demon.co.uk>
User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: freebsd-fs@freebsd.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: nfs server busy  lockup on 5.3
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jan 2005 12:46:45 -0000

Hi,

I've been experiencing a series of lockups of nfs recently which
normally require a reboot to clear.

Im about to submit a PR so any pointers on what I could check, trace or
dump would be helpful.

linux 2.6.8.1 nfs client copy or move of large files onto server causes
nfsd to lock. Any access from client of the mount causes those processes
to lock, and any access on the server to the directory containing the
destination file causes a lockup of that program.

I noted that systat -vmstat shows 25% disc usage and
75% cpu usage. The lockup usually occurs within a few 10's or 100's
of MBs of the first file. note files are 2-5GB.

A workaround and possible hint at the cause is to disable soft-deps,
that at least has enabled me to run the system in a stable manner.
The system has been stable for 2 weeks now with around 150+GB of
data transfered without problem.

system details:
nfs client is linux, slackware 10.0, 2.6.8.1 kernel with rpc workqueue
and rpc queue lock patches, 
http://client.linux-nfs.org/Linux-2.6.x/2.6.8.1/ (49 and 50 only)

Server FreeBSD 5.3 GENERIC, problem also present with recent cvsup
of 5.3. nfs exports are from a FFS1 file system on pst RAID array.
I also note that this system was running without this problem with 5.1.
The root partition is not on the pst array.

Simon