From owner-freebsd-stable@freebsd.org Mon Sep 12 15:23:41 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E471BBD837B for ; Mon, 12 Sep 2016 15:23:41 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::229]) (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 98B6D6AA for ; Mon, 12 Sep 2016 15:23:41 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: by mail-vk0-x229.google.com with SMTP id 16so120024980vko.2 for ; Mon, 12 Sep 2016 08:23:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=N4ZhJQg2EQt0fisKJnxd6ErWKff4sFhdRtKRXqAhZAg=; b=xtOCDMp3dOBmGb1rz3xtySJrEmEvRlQMUj6RRN0hvv7FguK4ycD9WlNu5J3GDp+nFB /ND/W2UOLLfRO0+AYpAaPJpJ9WM5koVaqwyUC/w7ir0r8SskKTh27ZnmQUp/WuCachz3 7HGUisjt1e9L/90otvML+lFk9xz8QMZrTuLmA5j5J5QsBYiBP411wsdX+iyqOufO49ZH oBrxLJZoZMhqWSWy+INd5ivxwrs+I/xCJ81AYYzLYzWenIL+F4u08/SqcpS+V1Gg7uw8 C0WYgIJxy4HpkVysWMb39DXLJIRW5f/rIfIZelWKJmFpKC3TOUWMgOGU8DvGE7U2c4Xw +R9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=N4ZhJQg2EQt0fisKJnxd6ErWKff4sFhdRtKRXqAhZAg=; b=MPWfSnr6Ux2ganghrFARTlA3Lw7HMvBnvf/U4SwvaBqlc+93J5Id/Vd0FXXEvOSH6P FNMD7XXuvRaiR2Mv2EZ2hi0/OxpnJ0Z2pw/mlHmTqO53h6clwrqDTfD3T1hcWaqjGx5z YtCLagGlGPFB3n95enVgEzjihyPq5r/xzD85stiYCSjwUrubL/BVO+ZvuKFR+Op6DLdV tmTjR47HvS1I+fD9I9xLrdUMtgESEGy+mrFXpyeo6fllctaAEjYyhqYqr+vpysvDRft/ RWaDFeocdMb6FZc+nAjTfhsC2TccDlKZxoLPL08bPELPxTV8y4Y3BxI6gmlk4a2SnGoD UqFA== X-Gm-Message-State: AE9vXwMBPaNJO1ZgJiV2qXX1or7jBEydScZmdnGv5PRD41kiCCVNflYBzlDwh3h1s4mDunYKG48v7l/OQfkB5Q== X-Received: by 10.31.136.70 with SMTP id k67mr13139213vkd.13.1473693819965; Mon, 12 Sep 2016 08:23:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.83.106 with HTTP; Mon, 12 Sep 2016 08:23:39 -0700 (PDT) In-Reply-To: References: <4996AF96-76BA-47F1-B328-D4FE7AC777EE@sarenet.es> From: Jim Harris Date: Mon, 12 Sep 2016 08:23:39 -0700 Message-ID: Subject: Re: Intel NVMe troubles? To: Borja Marcos Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2016 15:23:42 -0000 On Mon, Aug 1, 2016 at 11:49 AM, Jim Harris wrote: > > > On Mon, Aug 1, 2016 at 7:38 AM, Borja Marcos wrote: > >> >> > >> > It looks like all of the TRIM commands are formatted properly. The >> failures do not happen until about 10 seconds after the last TRIM to eac= h >> drive was submitted, and immediately before TRIMs start to the next driv= e, >> so I'm assuming the failures are for the the last few TRIM commands but >> cannot say for sure. Could you apply patch v2 (attached) which will dum= p >> the TRIM payload contents inline with the failure messages? >> >> Sure, this is the complete /var/log/messages starting with the system >> boot. Before booting I destroyed the pool >> so that you could capture what happens when booting, zpool create, etc. >> >> Remember that the drives are in LBA format #3 (4 KB blocks). As far as I >> know that=E2=80=99s preferred to the old 512 byte blocks. >> >> Thank you very much and sorry about the belated response. > > > Hi Borja, > > Thanks for the additional testing. This has all of the detail that I nee= d > for now. > > -Jim > > > There is an updated DCT 3.0.2 at: https://downloadcenter.intel. com/download/26221/Intel-SSD-Data-Center-Tool which has a fix for this issue. Borja has already downloaded this update and confirmed it looks good so far. Posting the update and results here so it is archived on the STABLE mailing list. Thanks, -Jim