From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 14:24:18 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 B5A768E5 for ; Fri, 15 Mar 2013 14:24:18 +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 2AA973C8 for ; Fri, 15 Mar 2013 14:24:17 +0000 (UTC) Received: (qmail 66578 invoked from network); 15 Mar 2013 15:36:18 -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 ; 15 Mar 2013 15:36:18 -0000 Message-ID: <51432F0D.2040002@freebsd.org> Date: Fri, 15 Mar 2013 15:24:13 +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: "Eggert, Lars" Subject: Re: NewNFS vs. oldNFS for 10.0? References: <514324E8.30209@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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:24:18 -0000 On 15.03.2013 15:01, Eggert, Lars 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 total wedge of all interfaces certainly shouldn't happen. This smells like blocking on a lock on a socket_upcall() thereby wedging tcp_input. I don't know the lockd code so maybe Rick knows how this could happen. -- Andre > 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'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 _______________________________________________ freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >