From owner-freebsd-stable@FreeBSD.ORG Sat Mar 11 02:08:51 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0595516A5A9 for ; Sat, 11 Mar 2006 02:08:50 +0000 (GMT) (envelope-from grafan@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAD5147D50 for ; Fri, 10 Mar 2006 17:40:06 +0000 (GMT) (envelope-from grafan@gmail.com) Received: by xproxy.gmail.com with SMTP id t15so526219wxc for ; Fri, 10 Mar 2006 09:40:01 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=szEbSc4WhvcEAUTjtbLGlFeauwL3lslxBVJ2vg43wDcZ35slxCDf+A0buor5jkYrwcA0riIBpoL3+NtmBFsH4/Y9CrbOct6sq5zPuv80QyXizMka5g3ZCPvV1yCEAY5L/H7Th9tV2uZ9RgXmcVUgzewB6iKMtD2YCk6tPusHsyc= Received: by 10.70.108.18 with SMTP id g18mr53997wxc; Fri, 10 Mar 2006 09:40:00 -0800 (PST) Received: by 10.70.125.17 with HTTP; Fri, 10 Mar 2006 09:40:00 -0800 (PST) Message-ID: <6eb82e0603100940s7d505e26w5351d708b714aefe@mail.gmail.com> Date: Fri, 10 Mar 2006 12:40:00 -0500 From: "Rong-En Fan" To: stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: nfsclient process stucks in nfsaio X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Mar 2006 02:08:51 -0000 Hi, After upgrading several our nfs clients from 5.4-RELEASE to 6.0-RELEASE and some are now 6.1-PRERELEASE (a weeks ago). From time to time, we saw some processes stuck in nfsaio, and unkillable. These processes generate lots of traffic to nfs server (write to nfs, but nfs server's disk= does not really in write. from netstat, client sends ~100Mbps, on nfs server, io= stat does not show me ~12.5MB/s). The nfsd on the server side is either in RUN or in ufs state. Server is running 5.5-PRELEASE as of yesterday. Client mount options: rw,nosuid,bg,intr,nodev. Both client and server are running rpc.lockd, rpc.statd. I'm sure it's not related to any locking problems. I have another set of nfs server/client both running 6.0-RELEASE. And I can easily reproduce this situation on these two boxesnes, just by running dd if=3D/dev/zero of=3D/nfs/ooo bs=3D1m If I do not add bs=3D1m, it works fine. Of all the boxes I mentioned above, I did not do anything special to kernel config, i.e., they are GENERIC w/o unnecessary devices and w/ firewal. Basically, I can do anything on these two boxes (they are not in production mode). Any suggestion are welcome. Thanks, Rong-En Fan