From owner-freebsd-fs@FreeBSD.ORG  Thu Feb 19 13:02:29 2015
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 13FC035D
 for <freebsd-fs@freebsd.org>; Thu, 19 Feb 2015 13:02:29 +0000 (UTC)
Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com
 [209.85.223.182])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id D82221BD
 for <freebsd-fs@freebsd.org>; Thu, 19 Feb 2015 13:02:28 +0000 (UTC)
Received: by iecar1 with SMTP id ar1so9162920iec.11
 for <freebsd-fs@freebsd.org>; Thu, 19 Feb 2015 05:02:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=googlemail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=17bHzHp/ai7q9tB1/FTBVrs2CqcuXU3QIXZJP3fyMKE=;
 b=sUJrd5gt4q5MelqEfcePuV3kdv8XEmgN1hfHPxRPi1fosSEBe+5tbfiMpn1tg/RzRW
 TPKYU5DVYYECdUdZxGZ79KrJF9A/CnmueSLTrDSvZZLxwSzjdQ8tW3FkQz61LAJBb6Er
 RQcc1S7FF13Yc62RgfNzdspi2TyRPVtrgNZclvS7vB1mk/H/RsAVISo+V7/KSXxIS1Wa
 Chnq0IscQVIiVvxHkJecPnWK56VF+khJp+uhKOWcd8Hg+mAe3CGuoiTwuIH8xYmIEPKo
 EdDWEStzc9S+Jwsn7eDKkljX8jjk1SIN+d37SBk6kHnmuWE57ZFma2sws9G3Rx/P40Na
 6soA==
MIME-Version: 1.0
X-Received: by 10.107.16.226 with SMTP id 95mr5914064ioq.32.1424350942316;
 Thu, 19 Feb 2015 05:02:22 -0800 (PST)
Received: by 10.107.14.199 with HTTP; Thu, 19 Feb 2015 05:02:22 -0800 (PST)
In-Reply-To: <54E5D574.8020406@fuckner.net>
References: <54E5BB12.3060707@fuckner.net> <54E5CF6E.5030906@multiplay.co.uk>
 <54E5D574.8020406@fuckner.net>
Date: Thu, 19 Feb 2015 13:02:22 +0000
Message-ID: <CAFHbX1JQkgfZwY+2MSvQSZNyhBQQCUiwwGF50PTjfuMy_e1kHg@mail.gmail.com>
Subject: Re: Creating zpool on NVMe Disks takes forever
From: Tom Evans <tevans.uk@googlemail.com>
To: Michael Fuckner <michael@fuckner.net>
Content-Type: text/plain; charset=UTF-8
Cc: FreeBSD FS <freebsd-fs@freebsd.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2015 13:02:29 -0000

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