Re: svn commit: r237367 - head/sys/fs/nfsclient
--r53EL0ep1aWhd0Bx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sun, Jul 01, 2012 at 03:56:52PM +0200, Andreas Tobler wrote:
> On 01.07.12 15:41, Konstantin Belousov wrote:
> >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 directo=
ry.
> >>>>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?
> >ktrace -o <file on local fs> -i make installkernel
> >Then kdump and cut the lines around relevant failure.
>=20
> ktrace -f, right?
Right, but without -i it is useless.
>=20
> I placed the whole kdump here:
>=20
> http://people.freebsd.org/~andreast/dumped_installkernel.log
>=20
> It is not clear to me where the failure starts :)
Because logs do not contain tracepoints from the children.
See above about -i.
I asked about excerpt because I expect the proper log to have an order
of magnitude bigger size.
>=20
> >
> >>
> >>>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.
> >
> >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 reprodu=
ce
> >this locally.
>=20
> Ok. I try with an nfs obj too.
> Thanks.
> Andreas
>=20
--r53EL0ep1aWhd0Bx
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (FreeBSD)
iEYEARECAAYFAk/wg2cACgkQC3+MBN1Mb4j7SACggffoplTXGrmcYSo1Y4wRiJMe
sYkAoKr8pgaFrS1Xbvln9dqt26lTdA+b
=CMW7
-----END PGP SIGNATURE-----
--r53EL0ep1aWhd0Bx--
討論串 (同標題文章)
完整討論串 (本文為第 7 之 11 篇)：