Date: Sun, 1 Jul 2012 16:41:32 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Andreas Tobler <andreast@freebsd.org> 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: <20120701134132.GO2337@deviant.kiev.zoral.com.ua> In-Reply-To: <4FF0528E.50002@FreeBSD.org> References: <201206210926.q5L9Q6nR002030@svn.freebsd.org> <4FF03316.5050609@FreeBSD.org> <20120701120408.GM2337@deviant.kiev.zoral.com.ua> <4FF0528E.50002@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--+F7KmZy3b6vGqMLF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 01, 2012 at 03:37:18PM +0200, Andreas Tobler wrote: > 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 ? >=20 > I'd say so yes. When installing a kernel onto a nfs mounted fs then=20 > 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. >=20 > When doing a installworld, it was, also in both cases, ppc64/sparc64,=20 > the cc1 in libexec which failed. >=20 > >Might be, start with ktrace-ing the whole make invocation, including > >the children processes. >=20 > Some recipes how to start? ktrace -o <file on local fs> -i make installkernel Then kdump and cut the lines around relevant failure. >=20 > >I used buildworld on the NFS-mounted obj/ as the test for the changes. >=20 > Here the obj is local, only the src and the destination is on the=20 > nfs/netboot server. I just finished build on NFS obj/ and did several rounds of installs for world and kernel into nfs-mounted destdir. It seems I cannot reproduce this locally. --+F7KmZy3b6vGqMLF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAk/wU4sACgkQC3+MBN1Mb4i3zQCeILWD4lZ8UAw/yY8F6dc/rQ7W 8c0AoMCRA+RZbRgLb1YC6RZGu+9ffq5L =Mt7W -----END PGP SIGNATURE----- --+F7KmZy3b6vGqMLF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120701134132.GO2337>