From owner-freebsd-fs@freebsd.org Mon Mar 7 14:31:53 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4DC5AC087E; Mon, 7 Mar 2016 14:31:53 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AF52E77D; Mon, 7 Mar 2016 14:31:53 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1acwCB-0008IZ-Ki; Mon, 07 Mar 2016 15:31:45 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-arm@freebsd.org, freebsd-fs@freebsd.org Subject: Re: Unstable NFS on recent CURRENT References: <3DAB3639-8FB8-43D3-9517-94D46EDEC19E@gromit.dlib.vt.edu> Date: Mon, 07 Mar 2016 15:31:37 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <3DAB3639-8FB8-43D3-9517-94D46EDEC19E@gromit.dlib.vt.edu> User-Agent: Opera Mail/1.0 (Win32) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: 0.8 X-Spam-Status: No, score=0.8 required=5.0 tests=ALL_TRUSTED, BAYES_50, FUZZY_VPILL autolearn=disabled version=3.4.0 X-Scan-Signature: c09395f469c52153b963e4ff2d10f427 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Mar 2016 14:31:54 -0000 On Sun, 06 Mar 2016 02:57:03 +0100, Paul Mather wrote: > On my BeagleBone Black running 11-CURRENT (r296162) lately I have been > having trouble with NFS. I have been doing a buildworld and buildkernel > with /usr/src and /usr/obj mounted via NFS. Recently, this process has > resulted in the buildworld failing at some point, with a variety of > errors (Segmentation fault; Permission denied; etc.). Even a "ls -alR" > of /usr/src doesn't manage to complete. It errors out thus: > > ===== > [[...]] > total 0 > ls: ./.svn/pristine/fe: Permission denied > > ./.svn/pristine/ff: > total 0 > ls: ./.svn/pristine/ff: Permission denied > ls: fts_read: Permission denied > ===== > > On the console, I get the following: > > newnfs: server 'chumby.chumby.lan' error: fileid changed. fsid > 94790777:a4385de: expected fileid 0x4, got 0x2. (BROKEN NFS SERVER OR > MIDDLEWARE) > > > I am using a FreeBSD/amd64 10.3-PRERELEASE (r296412) as the NFS server. > On the BeagleBone Black, I am mounting /usr/src and /usr/obj via > /etc/fstab as follows: > > chumby.chumby.lan:/build/src/head /usr/src nfs rw,nfsv4 0 0 > chumby.chumby.lan:/build/obj/bbb /usr/obj nfs rw,nfsv4 0 0 > > > /build/src/head and /build/obj/bbb are both ZFS file systems. > > Has anyone else encountered this? It has only started happening > recently for me, it seems. Prior to this, I have been able to do a > buildworld and buildkernel successfully over NFS. > > Cheers, > > Paul. I cc this to freebsd-fs for you. Ronald.