https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227609
--- Comment #13 from Mark Millard <[email protected]> --- (In reply to Vladislav V. Prodan from comment #12) You do not indicate if your buildworld buildkernel was using -j1 or some other -jN figure. The larger the N the more memory space required. > Swap: 500M Total, 106M Used, 394M Free, 21% Inuse This can change far more rapidly than you can get updates to be displayed. Also, if the requested swap space is larger than the free space, the used figure will not go to zero temporarily but instead will stay unchanged. But it does help to have very frequent output to get an idea if one is getting close to running out. But the display has to have started before the problem occurs. Technically there can be allocation failures for internal tracking reasons instead of just the swap space on media. Having only around 400M free is not much margin for the swap space. > RAM - 2GB > SWAP - 500MB Having RAM+SWAP be only 2.5GB has be a problem for various vintages of FreeBSD, even for -j1 in some cases. But I do not have specifics for stable/12 -r369250 . > swap_pager_getswapspace(32): failed This type of message means that you really did reach the swap space limit (or an internal tracking limit). Material was kept in RAM that it was trying to write out to swap. As far as I can tell, you need either a smaller -jN figure or for the RAM+SWAP to be larger (or some combination of such). Also, are you using a swap partition(s)? A swap file? I strongly suggest only using partition(s) for swap. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206048 for why. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
