Date: Thu, 19 Feb 2015 18:23:36 +0100 From: Michael Fuckner <michael@fuckner.net> To: freebsd-fs@freebsd.org Subject: Re: Creating zpool on NVMe Disks takes forever Message-ID: <54E61C18.8070101@fuckner.net> In-Reply-To: <54E5F19A.3080804@kateley.com> References: <54E5BB12.3060707@fuckner.net> <54E5CF6E.5030906@multiplay.co.uk> <54E5D574.8020406@fuckner.net> <CAFHbX1JQkgfZwY%2B2MSvQSZNyhBQQCUiwwGF50PTjfuMy_e1kHg@mail.gmail.com> <54E5F19A.3080804@kateley.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/19/2015 03:22 PM, Linda Kateley wrote:
>
> On 2/19/15 7:02 AM, Tom Evans wrote:
>> 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.
> It would be nice to know what nvme you have so we know that the firmware
> for this particular one will be handled poorly?
It is 2x Intel P3700 (400GB, PCIe Card, FW: 8DV10130 and Bootloader
8B1B012D)- don't know how to extract this data in FreeBSD
root@s4l:~ # nvmecontrol devlist
nvme0: INTEL SSDPEDMD400G4
nvme0ns1 (381554MB)
nvme1: INTEL SSDPEDMD400G4
nvme1ns1 (381554MB)
Regards,
Michael!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54E61C18.8070101>