From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 02:13:41 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A95413DC; Sat, 16 Mar 2013 02:13:41 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 3EF23A9F; Sat, 16 Mar 2013 02:13:40 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqEEAL3UQ1GDaFvO/2dsb2JhbABDiDG8eoF9dIIqAQEBBAEBASArIAsbGAICDRkCKQEJJgYPBAEcBIdzDLBtklqBI4Eqixh8NAeCLYETA5Qdgj6BH49jgyYgMoEFNQ X-IronPort-AV: E=Sophos;i="4.84,855,1355115600"; d="scan'208";a="19269333" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu.net.uoguelph.ca with ESMTP; 15 Mar 2013 22:13:39 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id ED783B3F23; Fri, 15 Mar 2013 22:13:39 -0400 (EDT) Date: Fri, 15 Mar 2013 22:13:39 -0400 (EDT) From: Rick Macklem To: Andre Oppermann Message-ID: <1138560306.3963522.1363400019941.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <51432F0D.2040002@freebsd.org> Subject: Re: NewNFS vs. oldNFS for 10.0? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-current , Lars Eggert 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: Sat, 16 Mar 2013 02:13:41 -0000 Andre Oppermann wrote: > 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. > I'm afraid I can't help much. The lockd and all the NFS stuff (old and new) share the kernel rpc (sys/rpc) code and that is where the upcalls are. At a quick look at them, they do have to acquire a mutex, but it would be hard to believe that would take 30sec? Also, I think (I'm not familiar with the NLM, so I'm not sure) that the NLM normally uses UDP and not TCP. It is a separate protocol with different port#s etc than NFS. rick > -- > 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" > > > >