Date: Sun, 20 Aug 2023 08:45:41 -0700 From: Mark Millard <marklmi@yahoo.com> To: des@freebsd.org, "mav@freebsd.org" <mav@FreeBSD.org>, Graham Perrin <grahamperrin@freebsd.org>, kevin.bowling@kev009.com, pi@freebsd.org, Cy Schubert <Cy.Schubert@cschubert.com>, Mateusz Guzik <mjguzik@gmail.com> Cc: Current FreeBSD <freebsd-current@freebsd.org> Subject: Re: ZFS deadlock in 14 Message-ID: <A4B9965A-F975-436D-9822-54054C1B4B79@yahoo.com> References: <A4B9965A-F975-436D-9822-54054C1B4B79.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling_Sm=C3=B8rgrav <des_at_FreeBSD.org> wrote on
Date: Sun, 20 Aug 2023 13:00:27 UTC :
> Alexander Motin <mav@FreeBSD.org> writes:
> > Unfortunately I think the current code in main should still suffer
> > from this specific deadlock. cd25b0f740 fixes some deadlocks in this
> > area, may be that is why you are getting issues less often, but I
> > don't believe it fixes this specific one, may be you was just lucky.
>=20
> Yep, it took a while but I got a deadlock with unmodified 4f14d4b6b7.
Are any of you testing based on USE_TMPFS=3Dno and such, so that
ZFS handles all file system activity, while allowing multiple
builders to be active as well? In my case, I also have:
ALLOW_MAKE_JOBS=3Dyes
In my testing, pkg builds and then the other builders report
"Builder starting" but end up stuck waiting in a loop with
timeouts involved ("vlruwk") before ever reporting any more.
Some progress is made in the original builder before I
eventually stop poudriere-devel.
Am I the only one that gets such behavior for this kind of
context?
=3D=3D=3D
Mark Millard
marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A4B9965A-F975-436D-9822-54054C1B4B79>