Date: Mon, 08 Apr 2024 22:24:24 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 277992] mpr and possible trim issues Message-ID: <bug-277992-227-bRSw0077Vd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-277992-227@https.bugs.freebsd.org/bugzilla/> References: <bug-277992-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D277992 --- Comment #6 from mike@sentex.net --- OK, as suspected. I stopped the test, reset the TRIM method to ATA_TRIM, offlined the disk one by one and did a trim -f /dev/da[disk]p1 one by one a= nd resilvered the pool. After that, I got normal performance for 3.5 iterrati= ons and then its back to being super slow on writes Apr 8 14:39:47 r-14mfitest LOOP[21836]: starting Apr 8 15:00:59 r-14mfitest LOOP[30713]: ending job ran 1272 seconds (0:21:= 12) Apr 8 15:07:29 r-14mfitest LOOP[33450]: starting Apr 8 15:28:54 r-14mfitest LOOP[42451]: ending job ran 1285 seconds (0:21:= 25) Apr 8 15:31:55 r-14mfitest LOOP[43719]: starting Apr 8 15:53:22 r-14mfitest LOOP[52716]: ending job ran 1287 seconds (0:21:= 27) Apr 8 15:56:23 r-14mfitest LOOP[53996]: starting Apr 8 16:18:03 r-14mfitest LOOP[63083]: ending job ran 1300 seconds (0:21:= 40) Apr 8 16:21:04 r-14mfitest LOOP[64344]: starting Apr 8 16:55:39 r-14mfitest LOOP[78807]: ending job ran 2075 seconds (0:34:= 35) Apr 8 16:58:40 r-14mfitest LOOP[80073]: starting Apr 8 17:56:56 r-14mfitest LOOP[4539]: ending job ran 3496 seconds (0:58:1= 6) Apr 8 17:59:57 r-14mfitest LOOP[5796]: starting --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-277992-227-bRSw0077Vd>