From nobody Mon May 16 14:37:53 2022 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 055E31AD8F4B for ; Mon, 16 May 2022 14:38:02 +0000 (UTC) (envelope-from wayne@post.wayne47.com) Received: from post.wayne47.com (post.wayne47.com [198.11.56.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "post.wayne47.com", Issuer "post.wayne47.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4L220n1ZZlz3Q52 for ; Mon, 16 May 2022 14:38:01 +0000 (UTC) (envelope-from wayne@post.wayne47.com) Received: from post.wayne47.com (post.wayne47.com [198.11.56.11]) by post.wayne47.com (8.15.2/8.15.2) with ESMTPS id 24GEbraB007931 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 May 2022 10:37:54 -0400 (EDT) (envelope-from wayne@post.wayne47.com) Received: (from wayne@localhost) by post.wayne47.com (8.15.2/8.15.2/Submit) id 24GEbr84007930; Mon, 16 May 2022 10:37:53 -0400 (EDT) (envelope-from wayne) Date: Mon, 16 May 2022 10:37:53 -0400 From: Michael Wayne To: FreeBSD Hackers Cc: Mark Millard Subject: Re: Can not build kernel on 1GB VM Message-ID: <20220516143753.GY72471@post.wayne47.com> Mail-Followup-To: FreeBSD Hackers , Mark Millard References: <27171A11-13B1-48A8-AF46-605091E1093F.ref@yahoo.com> <27171A11-13B1-48A8-AF46-605091E1093F@yahoo.com> List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <27171A11-13B1-48A8-AF46-605091E1093F@yahoo.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Queue-Id: 4L220n1ZZlz3Q52 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of wayne@post.wayne47.com designates 198.11.56.11 as permitted sender) smtp.mailfrom=wayne@post.wayne47.com X-Spamd-Result: default: False [-0.69 / 15.00]; ONCE_RECEIVED(0.10)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:198.11.56.11]; NEURAL_HAM_LONG(-0.77)[-0.770]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[wayne47.com]; NEURAL_SPAM_MEDIUM(0.97)[0.973]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.999]; RCPT_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROMTLD(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers]; RCVD_COUNT_ONE(0.00)[1]; FORGED_SENDER(0.30)[freebsd07@wayne47.com,wayne@post.wayne47.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:2015, ipnet:198.11.56.0/24, country:US]; FROM_NEQ_ENVFROM(0.00)[freebsd07@wayne47.com,wayne@post.wayne47.com]; RCVD_TLS_ALL(0.00)[]; FREEMAIL_CC(0.00)[yahoo.com] X-ThisMailContainsUnwantedMimeParts: N More info. I am running UFS so the ZFS should not be an issue % pstat -s Device 1K-blocks Used Avail Capacity /dev/md99 1048576 0 1048576 0% % df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ufs/rootfs 25388500 17630840 5726580 75% / devfs 1 1 0 100% /dev On Sat, May 14, 2022 at 08:02:29AM -0700, Mark Millard wrote: > The way to know if out of swap might actually be involved > in the context are some other messages that do not of > themselves announce kills: > > swap_pager: out of swap space > swp_pager_getswapspace(. . .): failed > > If you are getting either of those 2, then you are actually > running out of swap space. Otherwise you are not. I am not getting either of those. Watching swap as ctfmerge runs up confirms that I am likely not running out of swap. Note also that I continue to run a kernel built with the suggested patch to /sys/vm/vm_pageout.c > If you are not the real reason is one of 4: Likely the swap device isn't responding within a "reasonable" time. (from another mail in this chain) > FYI: > > kernel: swap_pager: indefinite wait buffer: bufobj: . . ., blkno: . . ., size: . . . > > is for a swap read taking over 20 seconds (including > time when queued but waiting in the queue to start > the transfer). I got this message on 12.1. I am not getting it on 12.3 > /boot/loader.conf can use the likes of: > > vm.pageout_oom_seq=120 > vm.pfault_oom_attempts=-1 > #vm.pfault_oom_attempts= 3 > #vm.pfault_oom_wait= 10 > > I do not know if you have tried any of these. Quoting one of my old emails: On 12.1 I used sysctl to set > vm.pageout_oom_seq=120 > vm.pfault_oom_attempts=-1 > > There was no improvement. I still see processes getting killed due > to no swap space despite only 7-8 MB being reported used. It sorta > feels like it's not really able to use swap at all. > > Note that everything worked fine on 11.x, this is a new issue on 12. I have not tried this on 12.3, nor have I tried the other two. Will do.