From nobody Wed Apr 23 04:31:41 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 4Zj5m927Nxz5sjMm for ; Wed, 23 Apr 2025 04:31:53 +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 4Zj5m73sQWz3TMF for ; Wed, 23 Apr 2025 04:31:51 +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="O/4fuRoo"; 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=1745382702; bh=WwVhAsPnlF4lwxhA0tFD4PoWZx28mVVSLADjDjmmQKU=; h=Date:From:To:Subject:In-Reply-To:References; b=O/4fuRooMoq7mi8QqUCo+9g/YocZYpcccoTGyn42C+C3w7H7RNRF3ojESjsnfi6uu FfYf6l3XrjUkbJLQNi54dnbAkghn3OSKeTblnf61zH0WvkvrCQD8SOsWrf5jSvfCXb maTy1G5hSjMkfffSDb8QiVvyQnOwmh/8MuQIasALzTlar2fO9MqRx0gALwaFKVrWW1 lTPeN2G3Xw44GPehDIAlGy/5EunOcyskucSBR0HdipuY1RpzA37n0F7g/k/2xnl1Xc xiAbmtDb/H+5s+v8sPkAkQTE6kMT3TPm7g1RanE2w5WR1xlXJlSD5TqidE1vLYPTXc eXy8yj1uFI55QsEVKwVbNgOcE4jigRUXWqEMmy60nM/NUdsKjgt9gEczIqyh38ULt2 W7viPCM5oyl0VeXKKvnUYxDSLjlpCsZu9SWf3MG/1f/ndvU9eW6SbgusHg2Qyd2Miv nU0AvW2+BPYGUjYH4oZBSgsy4wC2ZzTe43MDP9t9j6I2Ln8IS/M+GxQ8FqnxaoTE+e tS7a3+LuEkzRgIYZlZ1G6W2i/7MWK8PahG7YmekaYkaI9l2vtwu/+q8GRvfKIawpqN 7ewnH3qHh2d4MKlUmGvvqHNScORiB3hrQiWhLgsa0QzUUSQO9hQkSO3AtqUiFNNeG+ xXkPvMOnBDp3S9kJMIVxqv9k= 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 9A8455B3C9C for ; Wed, 23 Apr 2025 07:31:42 +0300 (EEST) Date: Wed, 23 Apr 2025 07:31:41 +0300 From: Sulev-Madis Silber To: freebsd-current@freebsd.org Subject: Re: zfs (?) issues? User-Agent: K-9 Mail for Android In-Reply-To: <61B5E2C7-EEF9-4DD8-8BB3-77B530FE1565@yahoo.com> References: <61B5E2C7-EEF9-4DD8-8BB3-77B530FE1565.ref@yahoo.com> <61B5E2C7-EEF9-4DD8-8BB3-77B530FE1565@yahoo.com> Message-ID: 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.41 / 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.984]; NEURAL_HAM_SHORT(-0.82)[-0.817]; DMARC_POLICY_ALLOW(-0.50)[ketas.si.pri.ee,reject]; ONCE_RECEIVED(0.20)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:7d0:8437:1300::/56]; R_DKIM_ALLOW(-0.20)[ketas.si.pri.ee:s=ketas-si-pri-ee-20240416002854-4096]; MIME_GOOD(-0.10)[text/plain]; NEURAL_SPAM_LONG(0.01)[0.010]; RCVD_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:3249, ipnet:2001:7d0::/32, country:EE]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_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: 4Zj5m73sQWz3TMF X-Spamd-Bar: + On April 23, 2025 6:27:20 AM GMT+03:00, Mark Millard = wrote: >Sulev-Madis Silber wrote on >Date: Wed, 23 Apr 2025 02:04:28 UTC : > >> yes, 2 * 8g partitions on separate disks, so i have 16g swap >>=20 >> =2E =2E =2E >>=20 >> >> >Van: Sulev-Madis Silber >> >> >Datum: maandag, 21 april 2025 03:25 >> >> >=2E =2E =2E >> >> >> >> >> >> others don't get it at all and only suggest adding more than 4g r= am >>=20 >> =2E =2E =2E > >I have no clue if this will be of any help=2E > >For 64-bit systems, having total SWAP much greater than, >say, 3=2E6*RAM normally produces a warning about potentially >being in a mistuned state=2E They look like, for example: > >warning: total configured swap (477183 pages) exceeds maximum recommended= amount (466816 pages)=2E >warning: increase kern=2Emaxswzone or reduce amount of swap=2E > >If I understand right, adjusting kern=2Emaxswzone makes other >tradeoffs that I do not know the details of=2E Thus I avoid >getting the messages by adjusting the SWAP space size >instead=2E I've been told that the messages suggest a higher >likelihood of deadlocks happening while managing the memory >space=2E(Others may known what they are doing with >kern=2Emaxswzone adjustments and could judge the tradeoffs=2E) > >Are you getting such messages on your console or >that you can see from "dmesg -a" or in >/var/log/messages ? > >(The detailed multiplier changes some from system >update to system update=2E I can not report a fixed >multiplier=2E I leave margin to make it unlikely that >I'd get the notice across various updates=2E) > >3=2E6 * 4 GiBytes =3D=3D 14=2E4 GiBytes SWAP, as an example=2E >Then RAM+SWAP =3D=3D 4=2E6*RAM, so 18=2E4 GiBytes or so as a >memory space=2E > > >=3D=3D=3D >Mark Millard >marklmi at yahoo=2Ecom > > i'm aware of that=2E but last time i checked it only affects possible swap= fragmentation=2E i tried to tune it according to some suggestions=2E then,= others suggested it not being thing to worry about so i took those things = off=2E i couldn't find good information of this=2E would this even affect a= ny of my issues=2E unless i'm wrong, i cause zfs to use all my ram up=2E wi= th certain specific actions=2E kernel won't freeze or panic=2E it just give= s zfs what it asks=2E that's my guess=2E and this is outside arc=2E it's of= ten told as if arc tuning is magic=2E i think nowadays it's not needed=2E i= read it=2E i see it my earlier poor attempts were in https://forums=2Efreebsd=2Eorg/threads/server-freezes-when-using-git-to-up= date-ports-tree=2E88651/ it also has outputs and others were confused as well=2E but some had same = issues so i'm curious if that got fixed=2E needs extra low ram tuning=2E or needs= some fix=2E maybe zfs fix=2E maybe tunable fix=2E maybe defaults change, u= nless it ruins someone else's system=2E that i don't like either as if we need something in kernel to check that whoa, 90% ram is used just= to power zfs=2E maybe we need to slow down here=2E i can't tell where memo= ry went=2E all i know i had this=2E and other issues finally someone suggested limiting git itself somehow=2E but i don't think= this is all=2E hell knows what it is=2E now i encountered some other issue= s isn't this kernel's job, ideally, to manage all this=2E including reservin= g some ram maybe=2E i can't even find tunables for this=2E i spent ages sea= rching and gave up multiple times=2E maybe i'm missing something that (z)fs= expert could easily see=2E i see that low ram zfs has improved a lot someh= ow=2E so something improved maybe i'll just wait? i clearly have not much clue left=2E research is har= d=2E maybe i'll manage to wrap my head around zfs eventually