From owner-freebsd-fs@FreeBSD.ORG  Thu Feb 19 13:13:10 2015
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 1DCE95B7
 for <freebsd-fs@freebsd.org>; Thu, 19 Feb 2015 13:13:10 +0000 (UTC)
Received: from mail-we0-f180.google.com (mail-we0-f180.google.com
 [74.125.82.180])
 (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 A8B3E2D2
 for <freebsd-fs@freebsd.org>; Thu, 19 Feb 2015 13:13:09 +0000 (UTC)
Received: by wevm14 with SMTP id m14so7156111wev.13
 for <freebsd-fs@freebsd.org>; Thu, 19 Feb 2015 05:13:02 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
 :subject:references:in-reply-to:content-type
 :content-transfer-encoding;
 bh=/OaB4aDdgpCLPKZ3vwmfHOzNKUG3sfWVu/mrqGNNSkw=;
 b=PD7OCNxWVeOzHNXBolWnCtaQd12BTksTHnw2WUvVwKbe3EbnbudCsG+ajHE3Ml8OSl
 Mb4VwwOPhEm4F6XEjY0qCq+Gg64FclGC6aMIKIvqdBZ4keXnP4TimwiRefpgBvGomFhH
 hKdAaLIcgI+QGUPI3qrn6WjeYBUEl+RGSPVG2XePgL3dkHVWF90I+EKmZa1etMLDa6wD
 aUcqjObX4bS2GjaxDmxDJNORiH2L49/ujbnZ+V0LyzNalXRUOpIofS5aqaQOJPN4Dg8W
 ZBVd4rfZDh+x4MkS7TnasBW8KpuSFJuwr/Nr+xNIsZaa7egByvgmr1QA3iqFKR92NNIP
 tXgw==
X-Gm-Message-State: ALoCoQkvgRCk9Il96zl2xymwexsCBJiAUvq2m/ECtUsn0QpPbiw6pS+s0UzY4kPMAVMff55qzguy
X-Received: by 10.194.108.162 with SMTP id hl2mr9242938wjb.134.1424351582337; 
 Thu, 19 Feb 2015 05:13:02 -0800 (PST)
Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk.
 [82.69.141.170])
 by mx.google.com with ESMTPSA id dt7sm24079510wib.19.2015.02.19.05.12.59
 for <freebsd-fs@freebsd.org>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Thu, 19 Feb 2015 05:13:00 -0800 (PST)
Message-ID: <54E5E159.1020407@multiplay.co.uk>
Date: Thu, 19 Feb 2015 13:12:57 +0000
From: Steven Hartland <killing@multiplay.co.uk>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
 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>
In-Reply-To: <54E5D574.8020406@fuckner.net>
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 <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:13:10 -0000


On 19/02/2015 12:22, 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?
Sounds like very bad / slow trim support in NVMe?

You might want to see what gstat -d -p shows