From nobody Sat Apr 26 13:06:16 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 4Zl92P4KpGz5vBC1 for ; Sat, 26 Apr 2025 13:06:21 +0000 (UTC) (envelope-from void@f-m.fm) Received: from fout-a8-smtp.messagingengine.com (fout-a8-smtp.messagingengine.com [103.168.172.151]) (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 4Zl92N29Pkz3XLK for ; Sat, 26 Apr 2025 13:06:20 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b=joxFVPXg; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=tIiaAfee; dmarc=pass (policy=none) header.from=f-m.fm; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 103.168.172.151 as permitted sender) smtp.mailfrom=void@f-m.fm Received: from phl-compute-04.internal (phl-compute-04.phl.internal [10.202.2.44]) by mailfout.phl.internal (Postfix) with ESMTP id B4ACD138084C for ; Sat, 26 Apr 2025 09:06:18 -0400 (EDT) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-04.internal (MEProxy); Sat, 26 Apr 2025 09:06:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm3; t=1745672778; x=1745759178; bh=+SVTNcsmQn 58hVqhVpFJ0Pq7Rsld2IhsKalgwrW6sCY=; b=joxFVPXg+107BTjUqm2WVU+Smh D/4MxpLsVfBwRLo8Gsq5NWDU7M9kDE0sGiFlgmMX0yuMaADOzvkmRC9VyuBSd1uQ La42EN90pWIaoo4cYPAM9j0iukcLvVEDMDgvn1zeuzjng9cYh50fh9e5rJz4mLOF ivYJdm1jbnfzbvQTzoi3fhbDn6Zu01202+Yif3jT/bd+lPS6d/eKF82HbAI7DKpS +qDJ6nNl7MP+iyWRop9qf9H1ycIfO7tlh5YS4hozRZIOBaM5yCB+84QQhyqkE+fC 4FguGTz1AeqH3eblu/yXlSoCD2SXKLUIKMV4fW8yYSIuBkev2JBpJi5iCFzg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1745672778; x=1745759178; bh=+SVTNcsmQn58hVqhVpFJ0Pq7Rsld2IhsKal gwrW6sCY=; b=tIiaAfee5suOlQEwl6wWxr4g/wD5hc2cqft/I83HTVWGZIBQFwQ WtIxuurnHCv+TNiK4Ey14eeyYW9BH6V4koFLRPDVKPIeU25c/rw0gEUHVlyBuGag V37677rEjedNezkxg73pqSYVDvmlcbcF2baZYKNKLbsWAwuw0FvFtO5UTwJJe2h1 mHiq9f6D9se12SxSUo4zAcUFk7y2jFI37L/+ZRM6kNitUHEkOuYYAfhslgx1UxVu 3UB/gqURpMugtttFI1wGhp3zpNiiTS4o2romxr7UQ2GOMpulinqXlRin5uANA7oK bg91qhPz/wENcyd10ZL2hHLXCEiKzZvTZsQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefvddrtddtgddvheehvdejucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggv pdfurfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhf fvuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehf qdhmrdhfmheqnecuggftrfgrthhtvghrnhepkeeluddvlefhieelfefggffhffektdehle elgfdugfdvgeekjeejuddtheehgfeunecuvehluhhsthgvrhfuihiivgeptdenucfrrghr rghmpehmrghilhhfrhhomhepvhhoihgusehfqdhmrdhfmhdpnhgspghrtghpthhtohepud dpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepfhhrvggvsghsugdqtghurhhrvghn thesfhhrvggvsghsugdrohhrgh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sat, 26 Apr 2025 09:06:18 -0400 (EDT) Date: Sat, 26 Apr 2025 14:06:16 +0100 From: void To: freebsd-current@freebsd.org Subject: Re: zfs (?) issues? Message-ID: Mail-Followup-To: freebsd-current@freebsd.org References: <56F52DF4-2988-4F06-9F53-90D07AF5DD02@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=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-1.15 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.998]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; NEURAL_SPAM_MEDIUM(0.45)[0.452]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:103.168.172.128/27]; RCVD_IN_DNSWL_LOW(-0.10)[103.168.172.151:from]; MIME_GOOD(-0.10)[text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_FROM(0.00)[f-m.fm]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US]; RCVD_TLS_LAST(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; FROM_HAS_DN(0.00)[] X-Rspamd-Queue-Id: 4Zl92N29Pkz3XLK X-Spamd-Bar: - On Sat, Apr 26, 2025 at 03:01:01PM +0300, Sulev-Madis Silber wrote: > >that might be it!? there is hdd on machine that was tested but now >never really likes to complete the long smart tests, and short take ages. >there are no "usual" disk errors, tho. that hdd is part of 2 disk mirror >that the git runs on These are exactly the symptoms that led me to junk 2x HDs. One was CMR the other SMR. Smart tests failing to execute normally is a sure sign it's hardware. >i'm wondering why noone else spots it much, tho? maybe they do but in the end attribute it to hardware >and this is not fixed on current either? and fix is in zfs? and ufs, >as tested by others, would not be affected... why? I've also seen the same thing happen in a microSD and a USB2/3 context, both were UFS2 not ZFS. >tl;dr - suspected issue of zfs on slow device filling up *entire* >ram with write buffers, leaving userland killed and system in unusable >state Going by what you've described here, I'd say the problem is down to hardware. --