Date: Thu, 19 Feb 2015 13:12:57 +0000 From: Steven Hartland <killing@multiplay.co.uk> To: freebsd-fs@freebsd.org Subject: Re: Creating zpool on NVMe Disks takes forever Message-ID: <54E5E159.1020407@multiplay.co.uk> In-Reply-To: <54E5D574.8020406@fuckner.net> References: <54E5BB12.3060707@fuckner.net> <54E5CF6E.5030906@multiplay.co.uk> <54E5D574.8020406@fuckner.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19/02/2015 12:22, Michael Fuckner wrote: > On 02/19/2015 12:56 PM, Steven Hartland wrote: >> Disable trim on init: >> sysctl vfs.zfs.vdev.trim_on_init=0 > this fixed it, thx! > > but why does it take >8h to trim 2x 400GB? Or is trimming handled > differently on NVMe than on HDD/SSD? Sounds like very bad / slow trim support in NVMe? You might want to see what gstat -d -p shows
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54E5E159.1020407>