From owner-freebsd-current@FreeBSD.ORG Mon Mar 18 12:43:31 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 1FB35F99 for ; Mon, 18 Mar 2013 12:43:31 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 86F9B892 for ; Mon, 18 Mar 2013 12:43:30 +0000 (UTC) Received: (qmail 113 invoked from network); 18 Mar 2013 13:54:58 -0000 Received: from unknown (HELO [62.48.0.94]) ([62.48.0.94]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 18 Mar 2013 13:54:58 -0000 Message-ID: <51470BEC.5090304@freebsd.org> Date: Mon, 18 Mar 2013 13:43:24 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: peter@holm.cc Subject: Re: NewNFS vs. oldNFS for 10.0? References: <1547734002.3937074.1363356520474.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <1547734002.3937074.1363356520474.JavaMail.root@erie.cs.uoguelph.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Rick Macklem , Lars Eggert , freebsd-current 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: Mon, 18 Mar 2013 12:43:31 -0000 On 15.03.2013 15:08, Rick Macklem wrote: > Lars Eggert wrote: >> Hi, >> >> this reminds me that I ran into an issue lately with the new NFS and >> locking for NFSv3 mounts on a client that ran -CURRENT and a server >> that ran -STABLE. >> >> 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 NFSv3, the client network stack became unresponsive on all >> interfaces for 30 or so seconds and e.g. SSH connections broke. The >> serial console remained active throughout, and the system didn't >> crash. About a minute after the wedgie 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 the default...) >> > I've mentioned limitations w.r.t. the design of the NLM protocol (rpc.lockd) > before. Any time there is any kind of network topology issue, it will run > into difficulties. There may also be other issues. > > However, since both the old and new client use the same rpc.lockd in the > same way (the new one just cribbed the code from the old one), I think > the same problem would exist for the old one. As such, I don't believe > this is a regression. Maybe we can talk Peter Holm into periodically running his file system stress test suite against NFS too? :-) Peter? -- Andre