From owner-freebsd-current@freebsd.org Mon Mar 29 08:50:27 2021 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AE71C5C136B for ; Mon, 29 Mar 2021 08:50:27 +0000 (UTC) (envelope-from se@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F85rM4Fk0z4pP7; Mon, 29 Mar 2021 08:50:27 +0000 (UTC) (envelope-from se@freebsd.org) Received: from Stefans-MBP-449.fritz.box (p200300cd5f31b200e86ec291004cfe28.dip0.t-ipconnect.de [IPv6:2003:cd:5f31:b200:e86e:c291:4c:fe28]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: se/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 0E87B27664; Mon, 29 Mar 2021 08:50:26 +0000 (UTC) (envelope-from se@freebsd.org) To: Andrea Venturoli References: <58bea0f0-5c3d-4263-ebee-f939a7e169e9@freebsd.org> From: Stefan Esser Cc: freebsd-current@freebsd.org Subject: Re: Strange behavior after running under high load Message-ID: Date: Mon, 29 Mar 2021 10:50:25 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="qfsWSMBaIEy3av67eQkgqrMZ4FvWM3NMj" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2021 08:50:27 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --qfsWSMBaIEy3av67eQkgqrMZ4FvWM3NMj Content-Type: multipart/mixed; boundary="h2mGZfMBb9js8m8LK7ByjNMGM2VFWTTRQ"; protected-headers="v1" From: Stefan Esser To: Andrea Venturoli Cc: freebsd-current@freebsd.org Message-ID: Subject: Re: Strange behavior after running under high load References: <58bea0f0-5c3d-4263-ebee-f939a7e169e9@freebsd.org> In-Reply-To: --h2mGZfMBb9js8m8LK7ByjNMGM2VFWTTRQ Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable Am 29.03.21 um 08:45 schrieb Andrea Venturoli: > On 3/28/21 4:39 PM, Stefan Esser wrote: >> After a period of high load, my now idle system needs 4 to 10 seconds = to >> run any trivial command - even after 20 minutes of no load ... >=20 > High CPU load or high disk load? High CPU load, 3 times the number of CPU threads in this particular batch run. Less than 10 files of less than 100 KB per second have been written. > ZFS? Snapshots? ZFS and automatic snapshots of the file system every hour. > 12.x? 13.x? -CURRENT as of some 24 hours before the issue occurred: FreeBSD 14.0-CURRENT #33 main-n245694-90d2f7c413f9-dirty: Sat Mar 27 15:3= 5:37=20 CET 2021 > I've seen something similar: after a high load period, system crawled s= o much=20 > that services were not answering in a reasonable time (e.g. mail would = fail=20 > with "no such mailbox"!). Program start-up was very slow, but interactive response once running was= normal (e.g. execution of internal shell commands like "echo *"). > Even rebooting didn't fix it, until I deleted some autosnapshots. Rebooting fixed it on my case. > top or other tools would show no disk activity, although the disks were=20 working=20 > as mad. No disk activity in my case. The system was idle without any load, but th= e issue persisted over many hours (up to the moment when I decided to reboo= t the system to get it back into a usable state). > Not sure it's the same case you experienced, though. Probably not, but you seem to have hit another case were a resource limit= was reached and the system did not gracefully deal with the situation. Thanks for replying ... Regards, STefan --h2mGZfMBb9js8m8LK7ByjNMGM2VFWTTRQ-- --qfsWSMBaIEy3av67eQkgqrMZ4FvWM3NMj Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmBhlNEFAwAAAAAACgkQR+u171r99UTg OAgAzR7f5wNC8Br9Ql6DarL2z2XMWuTDXr13grargu5TP7L+LD0F/d+m21XOjPQ9SyQQRVenrA+I Y++BOApz/OLcROK9Eiii2fd1Ln3wtmCoksp6xVcmgBtZOqbq95qPjU4uJtjUhBdVq8smK9Xtt94q ZDBknBrYzuKr8uSbYrGhq+1uNEIUrRz7adO74YWoOFXCj2B0tKQqZaiyqAXx9tgLHwoQx/IvBHcC jNQ8mTuEAIqWvHZuc/xOiPMJov8AEWB+GdRre70bAOBrYOh8t0PY25g3+SpGfbHPRosGmE2i0Qc+ R5q6hbFtKwl6Ns0eZQebdr5OPVaXn+9T+Hx3gyuAhg== =thoZ -----END PGP SIGNATURE----- --qfsWSMBaIEy3av67eQkgqrMZ4FvWM3NMj--