From owner-freebsd-current@FreeBSD.ORG Wed Apr 8 22:29:06 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 976AB1065670 for ; Wed, 8 Apr 2009 22:29:06 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-fx0-f167.google.com (mail-fx0-f167.google.com [209.85.220.167]) by mx1.freebsd.org (Postfix) with ESMTP id 285C78FC0A for ; Wed, 8 Apr 2009 22:29:05 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by fxm11 with SMTP id 11so336017fxm.43 for ; Wed, 08 Apr 2009 15:29:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=rFnot0KYiznsu62ebMir1Zy7Pb8KF+IKsTkuF9BcqY4=; b=rbfQ7NRf+8l7eD58/txjZwSgxHJ5Ct9lT+iYI2fGPPXcd8ZW1c4Ti2F4PAwB/JhsaT iQ11I1FohZazuIF6xGlno/3eg8i6yRznXdA6PVlxHYvRS0qYF47npLoI5WHfkLw/oz34 4EjzSnZuncAVFQXAIR6caaGd9hIsSUfdz//oo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=YzJwhwlSD06LIW3uO/tQeUyEWGRfL8/zQx75+RN8G1Y65SVJluFLSZYoGTj7Qth+53 l5oeOFj1Njevv+6Og81QqBbM9my6cjzAtoPBTMcbTfRxSspEmJe9l18JpQOMuwr/P6zd VWdkFQ3SSJbIBm3xDJCFT43uJ7tldWEkNpPKs= MIME-Version: 1.0 Received: by 10.223.109.198 with SMTP id k6mr542820fap.46.1239228319653; Wed, 08 Apr 2009 15:05:19 -0700 (PDT) In-Reply-To: <49D851FC.4090103@sdf.lonestar.org> References: <49D851FC.4090103@sdf.lonestar.org> Date: Wed, 8 Apr 2009 18:05:19 -0400 Message-ID: From: Ryan Stone To: Tom McLaughlin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: current@freebsd.org Subject: Re: NFS lockd/statd lock up network connection X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Apr 2009 22:29:06 -0000 > em0: Could not setup receive structures The em driver prints this out when it can't allocate mbufs or clusters. Can you show the output of vmstat -z? This error is indicative of a leak of mbufs or clusters, or a misconfiguration(too few mbufs or clusters). Ryan Stone