Date: Sat, 26 Apr 2025 14:06:16 +0100 From: void <void@f-m.fm> To: freebsd-current@freebsd.org Subject: Re: zfs (?) issues? Message-ID: <aAzaSNKoOT20D_F1@int21h> In-Reply-To: <BDA46DBC-34D4-4C79-9510-8960D195A206@ketas.si.pri.ee> References: <56F52DF4-2988-4F06-9F53-90D07AF5DD02@ketas.si.pri.ee> <aAkJ_EoizNYkntnh@int21h> <BDA46DBC-34D4-4C79-9510-8960D195A206@ketas.si.pri.ee>
index | next in thread | previous in thread | raw e-mail
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. --home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aAzaSNKoOT20D_F1>