From owner-freebsd-fs@FreeBSD.ORG Thu Apr 16 15:49:48 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3FD071B1 for ; Thu, 16 Apr 2015 15:49:48 +0000 (UTC) Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 025C5DFA for ; Thu, 16 Apr 2015 15:49:48 +0000 (UTC) Received: by iejt8 with SMTP id t8so54611101iej.2 for ; Thu, 16 Apr 2015 08:49:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=1dkMf76VZOMd4E/98jG1KnQ/PmBESd3edreFtc7o8hE=; b=Z3kWWfO1aso9MlHeEjwAp/N1bnoKflkIRsLtSzHtwAEyZEz8q5PU3ntDFkQtd3kNS/ rgkVfN2+WuIjWnFJsXa1VEQDAWvymcQdGYpkN0kRFClbAmulgDDl3x73QUvzYJCoTcpA fWpTq62qZriZAsvZmMxvwvFYwjxbqFAHxp3I6HXPMnEhW1xK6hOR8JPqiCGUPh6fIHZ3 weeFpjBeEJBBCpeGnsiBxru2WmGR7HHuG1ifWsj72t9V+hRkhfIlenEmQCrmU7MiZ1eB 65VEAKmW/yUgCgi68gkApW/SPs5F0hh+6bLElaKFIn0WEJHgDv005KaALRXwla0MxQY0 T+rg== MIME-Version: 1.0 X-Received: by 10.43.60.14 with SMTP id wq14mr38491874icb.60.1429199387445; Thu, 16 Apr 2015 08:49:47 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.36.67.2 with HTTP; Thu, 16 Apr 2015 08:49:47 -0700 (PDT) In-Reply-To: <718753704.19327489.1429107495125.JavaMail.root@uoguelph.ca> References: <718753704.19327489.1429107495125.JavaMail.root@uoguelph.ca> Date: Thu, 16 Apr 2015 11:49:47 -0400 X-Google-Sender-Auth: zrM4dSIL4pJbra25JfLDhPHBdgw Message-ID: Subject: Re: FreeBSD 10.1 can't "make -j5 buildworld" over NFS? From: J David To: Rick Macklem Cc: "freebsd-fs@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Apr 2015 15:49:48 -0000 On Wed, Apr 15, 2015 at 10:18 AM, Rick Macklem wrote: > Well, the NFS client is almost identical in the two systems. (A couple > of NFSv4 specific changes and a removal of a redundant check for creation > of a hard link across mount points are the only ones I can see.) > > As such, I'd suspect userland differences. There is a different "make" > in 10 (which I don't think is in 9.3?), so this would be a good starting > point. That may be, but this problem only occurs over NFS. It does not happen with local UFS or ZFS. So perhaps the new make is exercising the NFS client differently than the old one, revealing the problem. > Btw, "stale NFS file handle" means that the file has been deleted on the > server. Yes it does. And the make always dies during cleandir, during which things are being aggressively deleted. It does seem like that's the *only* stage that has problems. I.e. if "make cleanworld" is run before "make -j5 buildworld" then the parallel build will succeed. Hopefully that means it will be relatively easy to narrow down / reproduce the problem behavior. However, in my experience, stale NFS file handles usually occur when one client deletes things out from under another client (and/or after a server reboot, which is not the case here). In this case, this is the only client that can even mount the relevant partition as read-write, much less writing to it. It's like the 10.1 client is caching that stuff exists even after it removes it, leading to errors from the server when it tries to access them again. It's pretty unusual (again, in my experience) for a single client to trip over *itself* when deleting things. Thanks!