Date: Thu, 19 Feb 2015 13:02:22 +0000 From: Tom Evans <tevans.uk@googlemail.com> To: Michael Fuckner <michael@fuckner.net> Cc: FreeBSD FS <freebsd-fs@freebsd.org> Subject: Re: Creating zpool on NVMe Disks takes forever Message-ID: <CAFHbX1JQkgfZwY%2B2MSvQSZNyhBQQCUiwwGF50PTjfuMy_e1kHg@mail.gmail.com> 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 Thu, Feb 19, 2015 at 12:22 PM, Michael Fuckner <michael@fuckner.net> 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? TRIM/UNMAP is simply an SATA/SCSI command that is sent to a device. What the device does when it gets that command is up to the controller and firmware on the device. Cheers Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFHbX1JQkgfZwY%2B2MSvQSZNyhBQQCUiwwGF50PTjfuMy_e1kHg>