From nobody Wed Apr 23 06:55:06 2025 X-Original-To: freebsd-current@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 4Zj8xY63QLz5svrn for ; Wed, 23 Apr 2025 06:55:13 +0000 (UTC) (envelope-from freebsd-current-freebsd-org111@ketas.si.pri.ee) Received: from mail.ketas.si.pri.ee (d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13e8:21e:bff:fea2:d004]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Zj8xW4B7Wz3Ry1 for ; Wed, 23 Apr 2025 06:55:11 +0000 (UTC) (envelope-from freebsd-current-freebsd-org111@ketas.si.pri.ee) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ketas.si.pri.ee header.s=ketas-si-pri-ee-20240416002854-4096 header.b=vvDAHAeL; dmarc=pass (policy=reject) header.from=ketas.si.pri.ee; spf=pass (mx1.freebsd.org: domain of freebsd-current-freebsd-org111@ketas.si.pri.ee designates 2001:7d0:8437:13e8:21e:bff:fea2:d004 as permitted sender) smtp.mailfrom=freebsd-current-freebsd-org111@ketas.si.pri.ee X-Original-To: freebsd-current@freebsd.org DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ketas.si.pri.ee; s=ketas-si-pri-ee-20240416002854-4096; t=1745391308; bh=2z6mflP69h3Yi2rhdCjrELe3ADMAvcnctnvqqjx8e/I=; h=Date:From:To:Subject:In-Reply-To:References; b=vvDAHAeLKd0hZLpAyJUijUfJ9U2vRqeki+oreA78LHbLBvZLgb5p7ZcPj4mEwoerf QHiAaNIsWrtBeR/UaESp1qFDWUkJVcK1a74UY4nneU5mwajCLhbOJuR3TzqO7L0/5y QHr3htzF5C+C40PtwAK15n0l8/7PaTTiL+No/FwaTdOtepK3yXRoPj1QEZLJCxek17 upN/wbRcHFiKCQOg/Pttj0f+oML+VYtdKyV0G2fbrgDFGMox4jrgNJ4+YTlli2xi6/ wnalfmoa2jT56zQGpVmemI/mKWVXpaQsvOfOjDC+meO3OnmRlnblj6nXZH9mo6j/8m rbLd9XLWwaqDzi8nfSS9xX6UPyobZh5EuHK/0efuBYvzfwaWenHnlwsJZOOZWN+oOA DbPzC+/rd9GRU27qw5MKAtxMZLTI6VLg984JUZrr2lsd6+FFzI5RdRScQi4rtowMZq USe7kS7gKDTVm7x9sfaeW3bFoR+FLkA//R77LYLRfOcoBx/vWNd99h/iBVXWQdiWZb RBMva0dj6tTIt9T35mCoLE2iXF3FrSRVsaCNDvF4/0mW9R6SwZNGcw1OIOwbFPR0aY 92q0HeSuLhdgeIC7nKrnFQbaB8x5MfuRY4JS5anPt85VLqDLQIUmZgP8txa7t7jgHg 7ZJNYWwyjKlHgjQ1lC+LXrE0= Received: from [IPv6:::1] (0114-0000-0000-0000-13c8-8437-07d0-2001.dyn.estpak.ee [IPv6:2001:7d0:8437:13c8::114]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ketas.si.pri.ee (Postfix) with ESMTPSA id 10D555B4495 for ; Wed, 23 Apr 2025 09:55:08 +0300 (EEST) Date: Wed, 23 Apr 2025 09:55:06 +0300 From: Sulev-Madis Silber To: freebsd-current@freebsd.org Subject: Re: zfs (?) issues? User-Agent: K-9 Mail for Android In-Reply-To: References: <7FBFC21C-2E5E-409B-AACC-6C529F46B52A@yahoo.com> Message-ID: <2DED0D7F-2680-4826-A3B3-28425E26FCAB@ketas.si.pri.ee> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [1.36 / 15.00]; HFILTER_HOSTNAME_5(3.00)[d004-fea2-0bff-021e-13e8-8437-07d0-2001.dyn.estpak.ee]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-0.98)[-0.982]; NEURAL_HAM_SHORT(-0.78)[-0.777]; DMARC_POLICY_ALLOW(-0.50)[ketas.si.pri.ee,reject]; R_DKIM_ALLOW(-0.20)[ketas.si.pri.ee:s=ketas-si-pri-ee-20240416002854-4096]; ONCE_RECEIVED(0.20)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:7d0:8437:1300::/56]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-0.08)[-0.081]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:3249, ipnet:2001:7d0::/32, country:EE]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[ketas.si.pri.ee:+] X-Rspamd-Queue-Id: 4Zj8xW4B7Wz3Ry1 X-Spamd-Bar: + On April 23, 2025 8:34:36 AM GMT+03:00, Mark Millard = wrote: >On Apr 22, 2025, at 21:59, Mark Millard wrote: > >> Sulev-Madis Silber wrote on >> Date: Wed, 23 Apr 2025 04:31:41 UTC : >>=20 >> https://forums=2Efreebsd=2Eorg/threads/server-freezes-when-using-git-to= -update-ports-tree=2E88651/ >>=20 >> That, in turn mentions: >>=20 >> the remote console shows an unresponsive, frozen OS, unable to interact= with=2E it wasn't clear what happened there=2E but here icmp echo replies still ca= me back last i tried=2E i didn't try to do it deliberately once i found out= it's git >>=20 >>=20 >> If FreeBSD 13=2E4 can still swapping out process kernel >> stacks, you may want the likes of /etc/sysctl=2Econf >> to have: >>=20 >> # >> # Together this pair avoids swapping out the process kernel stacks=2E >> # This avoids processes for interacting with the system from being >> # hung-up by such=2E >> vm=2Eswap_enabled=3D0 >> vm=2Eswap_idle_enabled=3D0 would it be related here? >>=20 >> (I've no clue that that is why you lost control but >> it may be a possibility=2E) >>=20 >> (main [FreeBSD 15] no longer does such swapping out of any >> process kernel stacks and the 2 settings have been removed=2E) > >Are you using a file system based SWAP space? Vs=2E a >Partition or Slice based SWAP space? just 2 gpt partitions > >Quoting: > >https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D206048#c7 > >on why it should be Partition/Slice based: > >QUOTE >On 2017-Feb-13, at 7:20 PM, Konstantin Belousov wrote >on the freebsd-arm list: > >=2E =2E =2E > >swapfile write requires the write request to come through the filesystem >write path, which might require the filesystem to allocate more memory >and read some data=2E E=2Eg=2E it is known that any ZFS write request >allocates memory, and that write request on large UFS file might require >allocating and reading an indirect block buffer to find the block number >of the written block, if the indirect block was not yet read=2E > >As result, swapfile swapping is more prone to the trivial and unavoidable >deadlocks where the pagedaemon thread, which produces free memory, needs >more free memory to make a progress=2E Swap write on the raw partition ov= er >simple partitioning scheme directly over HBA are usually safe, while e=2E= g=2E >zfs over geli over umass is the worst construction=2E >END QUOTE > >Note the references to ZFS and GELI=2E Your forum notes reference such=2E > > >A separate tunable: in case "was killed: failed to reclaim memory" >is involved but not reported/recorded: in /boot/loader=2Econf > ># ># Delay when persistent low free RAM leads to ># Out Of Memory killing of processes: >vm=2Epageout_oom_seq=3D120 helpful here? > > > >Separate question: why did some forum top runs show >qemu-system-arm threads? That could be a significant >competition for RAM+SWAP=2E it's small vm yes=2E but it behaves well=2E part of it gets swapped out=2E= then back in, so on it's all funny, i might be using more things in that machine than i have r= am for=2E but it just gets swapped out=2E swapping it back in causes delay = in that thing that needs that=2E like always i still think git does something here=2E if i don't touch git, everything = is absolutely perfect=2E why git? if i restrain it from config, it seems to= not cause issues=2E except maybe they are hidden now whatever happens, it happens in memory that is impossible to swap out or i= s not preferred to swap out git is not swapping and then being killed=2E that's not how it will affect= the system=2E i think i helps zfs to take all memory and either throw unus= ual errors, like that single case=2E or just cause total exhaustion what's fun is it never appears elsewhere=2E everything else seems to work = as one would expect it to work when low rammed > > >=3D=3D=3D >Mark Millard >marklmi at yahoo=2Ecom > > p=2Es: i also found https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D231457 where people experince (maybe) similar issues many years ago is it active issue still?