Date: Wed, 23 Jul 2025 01:42:02 -0700 From: Mark Millard <marklmi@yahoo.com> To: FreeBSD Mailing List <freebsd-ports@freebsd.org>, FreeBSD Toolchain <freebsd-toolchain@freebsd.org> Subject: Odd "swp_pager_getswapspace(??): failed"s happen during bulk -Ca for RAM+SWAP=704 GiBytes Message-ID: <D36C06CF-4A0E-4385-A403-029808E97776@yahoo.com> References: <D36C06CF-4A0E-4385-A403-029808E97776.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In a context with RAM+SWAP =3D 704 GiBytes (192 GiBytes being RAM, 512 GiBytes being SWAP) doing poudriere bulk -Ca builds at some point ends up with reports like: swp_pager_getswapspace(22): failed and: was killed: failed to reclaim memory for 12 builders, MAKE_JOBS_NUMBER=3D3 , TMPFS_BLACKLIST in use, 32 FreeBSD cpus, etc. For example: . . . Jul 22 10:17:27 7950X3D-ZFS kernel: pid 62915 (scc_16815), jid 780, uid = 0: exited on signal 11 (core dumped) Jul 22 21:38:10 7950X3D-ZFS kernel: ue0: link state changed to DOWN Jul 22 21:38:10 7950X3D-ZFS kernel: ue0: link state changed to UP Jul 22 21:38:29 7950X3D-ZFS kernel: swap_pager: out of swap space Jul 22 21:38:29 7950X3D-ZFS kernel: swp_pager_getswapspace(22): failed Jul 22 21:39:11 7950X3D-ZFS kernel: pid 15059 (dot), jid 780, uid 0, was = killed: failed to reclaim memory Jul 22 21:43:38 7950X3D-ZFS kernel: swap_pager: out of swap space Jul 22 21:43:38 7950X3D-ZFS kernel: swp_pager_getswapspace(14): failed Jul 22 21:44:04 7950X3D-ZFS kernel: pid 15049 (dot), jid 780, uid 0, was = killed: failed to reclaim memory Jul 22 21:56:39 7950X3D-ZFS kernel: swap_pager: out of swap space Jul 22 21:56:39 7950X3D-ZFS kernel: swp_pager_getswapspace(15): failed Jul 22 21:57:12 7950X3D-ZFS kernel: pid 15045 (dot), jid 780, uid 0, was = killed: failed to reclaim memory I've not figured out a way to track down such messages back to the relevant log file for the builds that were killed. Neither the pid, nor the jid appear in the log files. Similarly, nothing in /var/log/messages identifies the poudriere Job Id or other such. (I've never happened to be actively monitoring when the issue happened. So I've always ended up looking at it after the fact.) It would be nice to be able to identify what specific packages to try to rebuild for these --and to investigate why the SWAP usage that had stayed under 2 GiByte ended up reaching 512 GiBytes during that period. =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?D36C06CF-4A0E-4385-A403-029808E97776>