From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 14:02:01 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 42013430; Fri, 15 Mar 2013 14:02:01 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id 252EE28D; Fri, 15 Mar 2013 14:02:01 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,850,1355126400"; d="scan'208";a="31091599" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 15 Mar 2013 07:02:00 -0700 Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r2FE20jR003924; Fri, 15 Mar 2013 07:02:00 -0700 (PDT) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.218]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.02.0342.003; Fri, 15 Mar 2013 07:02:00 -0700 From: "Eggert, Lars" To: Andre Oppermann Subject: Re: NewNFS vs. oldNFS for 10.0? Thread-Topic: NewNFS vs. oldNFS for 10.0? Thread-Index: AQHOIYLPEsCxsg9cck2Q0y59+EQ/fpinPaKA Date: Fri, 15 Mar 2013 14:01:59 +0000 Message-ID: References: <514324E8.30209@freebsd.org> In-Reply-To: <514324E8.30209@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.104.60.116] Content-Type: text/plain; charset="us-ascii" Content-ID: <570D0F23741E6E4CB1284E4004CC4BA8@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "" , "" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Fri, 15 Mar 2013 14:02:01 -0000 Hi, this reminds me that I ran into an issue lately with the new NFS and lockin= g for NFSv3 mounts on a client that ran -CURRENT and a server that ran -STA= BLE. When I ran "portmaster -a" on the client, which mounted /usr/ports and /usr= /local, as well as the location of the respective sqlite databases over NFS= v3, the client network stack became unresponsive on all interfaces for 30 o= r so seconds and e.g. SSH connections broke. The serial console remained ac= tive throughout, and the system didn't crash. About a minute after the wedg= ie I could SSH into the box again, too. The issue went away when I killed lockd on the client, but that caused the = sqlite database to become corrupted over time. The workaround for me was to= move to NFSv4, which has been working fine. (One more reason to make it th= e default...) I'm not really sure how to debug this further, but would be willing to work= with someone off-list who'd tell me what tests to run. Lars=