From owner-freebsd-fs@FreeBSD.ORG Thu Feb 19 17:24:07 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 18F59576 for ; Thu, 19 Feb 2015 17:24:07 +0000 (UTC) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::12]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9CEBE350 for ; Thu, 19 Feb 2015 17:24:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1424366617; l=1037; s=domk; d=fuckner.net; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References: Subject:To:MIME-Version:From:Date; bh=UDEWKPaWLORujI9E7/WvHYjJSw70IOWqPwIlIFJ6/hc=; b=GRedu5vfGypFzDcN0HIdfgcytET/QCuuxks14oK9i4qjqdYdN3ItfZGUJ9RTLqlaD2F GOx8+rHtcrSEesB1K6wkCeLRHTs+Mm+2UmqTRLrVITBnqCH4LJRmbwAMJGxjvrEOcD/Vk IM32cOQOddb1qO2x8+sca9OlQEOfeqcaRCM= X-RZG-AUTH: :IWUHfUGtd9+4Du6KUGxoqde+AFhxnvkTDzh0c7ueojHnW/eNeq6Kp+QhHthC/P//Lh5ODL9FqzyNNUxt0AH1XMoM3yHFZvvKg1MBwQ== X-RZG-CLASS-ID: mo00 Received: from localhost.localdomain (bras-pool-3.wtnet.de [IPv6:2a02:2028:22a:8241:e8b:fdff:fe76:e463]) by smtp.strato.de (RZmta 37.3 AUTH) with ESMTPSA id j00bc8r1JHNbEuZ (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) for ; Thu, 19 Feb 2015 18:23:37 +0100 (CET) Message-ID: <54E61C18.8070101@fuckner.net> Date: Thu, 19 Feb 2015 18:23:36 +0100 From: Michael Fuckner User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: Re: Creating zpool on NVMe Disks takes forever References: <54E5BB12.3060707@fuckner.net> <54E5CF6E.5030906@multiplay.co.uk> <54E5D574.8020406@fuckner.net> <54E5F19A.3080804@kateley.com> In-Reply-To: <54E5F19A.3080804@kateley.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2015 17:24:07 -0000 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 >> 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!