Creating zpool on NVMe Disks takes forever

[Xin Li]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 02/19/15 11:26, Mark Martinec 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.
> 
> 
> The default of vfs.zfs.vdev.trim_on_init = 1 can be 
> counterproductive in case of enabling encryption on a device.  The 
> FreeBSD handbook for example states:
> 
> 
> https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-encrypting.html

Encrypted
> 
GEOM providers does not support TRIM (neither pass-through
nor random initialization) right now, so this doesn't matter, at least
not yet.

Cheers,
- -- 
Xin LI <delphij at delphij.net>    https://www.delphij.net/
FreeBSD - The Power to Serve!           Live free or die
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.1.1 (FreeBSD)

iQIcBAEBCgAGBQJU5j0TAAoJEJW2GBstM+nsXJEP/3aT2VBSvBgB7m08STuv4PB6
7HHxb6a8MmSy94QGr19I3z+LaT3iIUjts/mncFyoatjYbRhd0DSiB4GUlnGr4PfK
X7Yf9hVFFyBA6JaOWUF1HSIq7ErXZjWwVRuRSjx4nxBv5h+4NedMfhrMOdJFHj/P
E9LzOUVwO1Chx0JjOFtf/U+72kbl75cyt/4eTo9WdTRn4k6JubedOBb5Q7AiXcq3
mROmNBwnD96s5zpx/9CjZ3fa8I7lQ14CWG6ca3MRRJlyg8ugfeGmJy6az8UOCZ/z
Nld16RFetK1quWiat+xiLTHAopF+5Wc6PGjOG092nsy8uo0ITJMcJE1gvadiOr73
r7d50vDtiDYCE8V/lR+TtKB2j8vuU1iDKf3E4thdmlwpWIb09gsLvm6hVhNf6Wok
4hhJm4kRDiaBj4La30zCmqx0/xi01XIL4IiKH3UXRI/Gjty0+fhg0SNtrXisZjSD
qBEeCgHoJ6BtC0kMHh70dmSgN41ElmqlA2SFXr+kJQY8Td68Cad0ZD7J2Jez4PgU
jQ4OzqVvnY1KhxBiaAGcNCdRGdgC8jzxwenGhUSBjPkBcconTjvu6itEDZCfWLAk
W5L7lFGf+CbvWF2ns/eu1OvCfQRIIX8i2m0mZk9yFDebSFTZkgPx0QC8B1NbZg1f
bZU5SFZ04EOYu04LVwx4
=juXu
-----END PGP SIGNATURE-----