Creating zpool on NVMe Disks takes forever

[Linda Kateley]

On 2/19/15 7:02 AM, Tom Evans wrote:
> On Thu, Feb 19, 2015 at 12:22 PM, Michael Fuckner <michael at 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.
It would be nice to know what nvme you have so we know that the firmware 
for this particular one will be handled poorly?
>
> Cheers
>
> Tom
> _______________________________________________
> freebsd-fs at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"

-- 
Linda Kateley
Kateley Company
Skype ID-kateleyco
http://kateleyco.com