To sum up what happened, Yamagi was kind enough to test several
patches and ultimately the issue got solved here
https://cgit.freebsd.org/src/commit/?id=e9272225e6bed840b00eef1c817b188c172338ee
. The patch also got merged into releng/13.0
On 3/17/21, Yamagi wrote:
> Hi,
> me and some other users
Thanks, I'm going to have to ponder a little bit.
In the meantime can you apply this:
https://people.freebsd.org/~mjg/maxvnodes.diff
Once you boot, tweak maxvnodes:
sysctl kern.maxvnodes=1049226
Run poudriere. Once it finishes, inspect sysctl vfs.highest_numvnodes
On 3/17/21, Yamagi wrote:
>
This time poudriere came to an end:
% sysctl vfs.highest_numvnodes
vfs.highest_numvnodes: 500976
On Wed, 17 Mar 2021 18:55:43 +0100
Mateusz Guzik wrote:
> Thanks, I'm going to have to ponder a little bit.
>
> In the meantime can you apply this:
>
Can you reproduce the problem and run obtain "sysctl -a"?
In general, there is a vnode limit which is probably too small. The
reclamation mechanism is deficient in that it will eventually inject
an arbitrary pause.
On 3/17/21, Yamagi wrote:
> Hi,
> me and some other users in the ##bsdforen.de
Hi Mateusz,
the sysctl output after about 10 minutes into the problem is attached.
In case that its stripped by Mailman a copy can be found here:
https://deponie.yamagi.org/temp/sysctl_vlruwk.txt.xz
Regards,
Yamagi
On Wed, 17 Mar 2021 15:57:59 +0100
Mateusz Guzik wrote:
> Can you reproduce the
