From owner-freebsd-fs@FreeBSD.ORG Thu Nov 11 22:54:44 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DD6A106564A for ; Thu, 11 Nov 2010 22:54:44 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 2B4EF8FC0A for ; Thu, 11 Nov 2010 22:54:43 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEANcC3EyDaFvO/2dsb2JhbACDO6ABsRCQb4EigVKBY3MEhFqFfoUP X-IronPort-AV: E=Sophos;i="4.59,185,1288584000"; d="scan'208";a="100457969" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 11 Nov 2010 17:54:42 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 06E9FB3EB0; Thu, 11 Nov 2010 17:54:43 -0500 (EST) Date: Thu, 11 Nov 2010 17:54:43 -0500 (EST) From: Rick Macklem To: Robert Schulze Message-ID: <865951441.196904.1289516082967.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <4CDBB9EB.8010908@bytecamp.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [12.16.49.138] X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - IE8 (Win)/6.0.7_GA_2473.RHEL4_64) Cc: freebsd-fs@freebsd.org Subject: Re: nfsd stuck in *rc_lock state X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Nov 2010 22:54:44 -0000 > Hello everybody, > > we are running several 8.1 NFS Clients connected to a 8.0 NFS Server. > The system ran fine, but today the NFS-Server locked up. > > nfsd ate 100% of CPU, with one {nfsd: service} thread in state > "*rc_lock". I tried to find others with the same issue and finally > ended > up at a patch from Rick: > > http://people.freebsd.org/~rmacklem/freebsd8.1-patches/replay.patch > > may I apply this patch to a 8.0 system to fix this issue, or are there > any other patches/commits which affect this? > That patch is "self contained", so I think it should be fine to apply it to an 8.0 server. You might also want http://people.freebsd.org/~rmacklem/freebsd8.0-patches/freebsd8-svc-mbufleak.patch which plugged an mbuf leak in the regular FreeBSD8.0 server. Good luck with it, rick