Date: Thu, 26 Mar 2020 15:06:49 -0700 From: bob prohaska <fbsd@www.zefox.net> To: Mark Millard <marklmi@yahoo.com> Cc: freebsd-arm@freebsd.org, bob prohaska <fbsd@www.zefox.net> Subject: Re: Belated out of swap kill on rpi3 at r359216 Message-ID: <20200326220649.GA99824@www.zefox.net> In-Reply-To: <0FF6BC4C-296F-49F3-8FB8-AA87A49349E2@yahoo.com> References: <20200324155753.GA91922@www.zefox.net> <83E41A13-6C24-4B56-A837-779044038FBC@yahoo.com> <20200324185518.GA92311@www.zefox.net> <75CE3C07-8A0A-4D32-84C6-24BEA967447E@yahoo.com> <20200324224658.GA92726@www.zefox.net> <764D5A86-6A42-44E0-A706-F1C49BB198DA@yahoo.com> <20200325015633.GA93057@www.zefox.net> <0FF6BC4C-296F-49F3-8FB8-AA87A49349E2@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Just to wrap up, I tend to agree that delays writing to the microSD filesystem were blocking swap traffic and causing OOM kills. Turning off OOM allowed the OS build/install to complete successfully. Why this behavior started recently is less clear. The card was placed in service in October of 2018 and has been in strenuous use since then. The first hints of trouble occurred in late 2019. Perhaps this phenomenon is a useful warning of impending wearout. The gstat logs are at http://www.zefox.net/~fbsd/rpi3/swaptests/r359216/ in case anybody's curious. Thanks for all your attention, bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200326220649.GA99824>