Date: Sun, 01 Jul 2012 15:37:18 +0200 From: Andreas Tobler <andreast@FreeBSD.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: svn commit: r237367 - head/sys/fs/nfsclient Message-ID: <4FF0528E.50002@FreeBSD.org> In-Reply-To: <20120701120408.GM2337@deviant.kiev.zoral.com.ua> References: <201206210926.q5L9Q6nR002030@svn.freebsd.org> <4FF03316.5050609@FreeBSD.org> <20120701120408.GM2337@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01.07.12 14:04, Konstantin Belousov wrote: > On Sun, Jul 01, 2012 at 01:23:02PM +0200, Andreas Tobler wrote: >> On 21.06.12 11:26, Konstantin Belousov wrote: >>> Author: kib >>> Date: Thu Jun 21 09:26:06 2012 >>> New Revision: 237367 >>> URL: http://svn.freebsd.org/changeset/base/237367 >>> >>> Log: >>> Enable deadlock avoidance code for NFS client. >> >> >> Hm, since this commit I fail with my nfs installworld/kernel. >> >> I have a builder which installs world/kernel to a nfs mounted directory. >> Namely used for cross builds. >> >> Now since this commit I get the following when I install kernel to the >> nfs directory: >> >> .. >> install -o root -g wheel -m 555 zfs.ko.symbols >> /netboot/sparc64/boot/kernel >> install: /netboot/sparc64/boot/kernel/zfs.ko.symbols: No such file or >> directory >> *** [_kmodinstall] Error code 71 >> .. >> >> The file is there, a local install of the tree works without problems. >> Reverting to r237366 also makes it work again. >> >> The server is a -CURRENT, r237880, The client, -CURRENT too. >> >> How can I help to track down the real issue? > > Is it always the same file in the install procedure which causes the > failure ? Even more, is the failure pattern always the same ? I'd say so yes. When installing a kernel onto a nfs mounted fs then always (in my cases) the zfs.ko.symbols was the failing pattern. I tried ppc64 and sparc64 as target. With both it was the above file. When doing a installworld, it was, also in both cases, ppc64/sparc64, the cc1 in libexec which failed. > Might be, start with ktrace-ing the whole make invocation, including > the children processes. Some recipes how to start? > I used buildworld on the NFS-mounted obj/ as the test for the changes. Here the obj is local, only the src and the destination is on the nfs/netboot server. Thanks, Andreas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FF0528E.50002>