Oh I hear you, and that was definitely where I pointed my finger at first. But I will
keep digging and see where the evidence takes me for now.
As an update, 5.2 with softdeps seems fine. 5.4 without softdeps, also fine. So
potentially a softdeps bug introduced between the two releases. I am churning
through a git bisect now and will hopefully have more solid data in the next day
or so.
On February 11, 2019 at 9:07 AM Matthew Dillon <[email protected]> wrote:
This feels more like an issue with the I/O and not with UFS specifically. But since you tried two different storage devices it couldn't be that. Perhaps there is a power or overheat issue on the system.-MattOn Sun, Feb 10, 2019 at 1:42 PM Eric Melville < [email protected]> wrote:Hello there,
After installing 5.4 my system has been getting stuck in UFS, apparently in softdeps.
At first I was faulting the -j12 buildworld, but then saw it in lower parallel counts, and
eventually saw it when looping buildworld with no -j option at all. Then I was faulting
my fast new NVME but eventually factored that out too by changing back to an old
hard drive. In any case, the faster the hardware and the more work running, the
more quickly and easily this seems to reproduce.
Typically during the phase that removes old output, the build will hang indefinitely.
Some processes continue to run but new ones never get going, and the old world
clean never makes any progress. For example ssh to the host in this state would
succeed to connect and authenticate, but the new shell never seems to run.
I suppose I should try disabling softdeps next.
