Date: Fri, 23 Feb 2024 12:58:07 -0500 From: mike tancsa <mike@sentex.net> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, freebsd-fs@freebsd.org Subject: Re: really slow problem with nvme Message-ID: <976b175e-4bef-4a87-99f6-bf71a1c69e5d@sentex.net> In-Reply-To: <5n117579-8259-3on3-90pn-79o8n52q4q32@yvfgf.mnoonqbm.arg> References: <5n117579-8259-3on3-90pn-79o8n52q4q32@yvfgf.mnoonqbm.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/23/2024 12:46 PM, Bjoern A. Zeeb wrote: > Hi, > > this is a Samsung SSD 970 EVO Plus 1TB nvme and gpart and newfs > were already slow (it took like two hours for newfs). > > Here's another example now: > > # /usr/bin/time mkdir foo > 1.82 real 0.00 user 0.00 sys > > How does one debug this? > Hi Bjoern, Can you do a destructive trim(8) to the device first to see if that makes a difference ? I had a similar oddly slow (although not as slow as your nvme) device that was fixed with a trim ---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?976b175e-4bef-4a87-99f6-bf71a1c69e5d>