From owner-freebsd-current@freebsd.org Fri Apr 15 19:22:52 2016 Return-Path: Delivered-To: freebsd-current@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 383D9AEDCF8 for ; Fri, 15 Apr 2016 19:22:52 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (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 0188E1B05 for ; Fri, 15 Apr 2016 19:22:52 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22b.google.com with SMTP id u185so144216444iod.3 for ; Fri, 15 Apr 2016 12:22:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=L5xmmQkAdHU+TVGfQb/MJ/mJrXpYTS9C07z+cTEXM3c=; b=SqoHCkla+jeEFzoig0Bjwo2cziuAO3mGGye+SpPvHU0RjUgmJOtlk/0/RJy/m3aHp1 wBDzGmsXno/2wTexkmvpycWTQV0T3Wb+rWYGbGJMTY4vxeVIONdJj5leD/Opove1KLGH RoWnswdL5pozYdy//ph+kYx7QUk4CWq6gEgjw/ehOOtqxAd4gjCvMJcGi5LTlYOZMUGa GRJnTGQGINWM3v/A3ClDUIEfeOw5SSzKxmHeE5l24kAxG3jAppxx4uBzitzeA9HZxvo6 aRKeZYri+T6QLQ9cenwNkzGcbwhy8/thnr5vWzlGol/9t8ed1cc8ECJSFCVD+fsu7Y8l 5Xpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=L5xmmQkAdHU+TVGfQb/MJ/mJrXpYTS9C07z+cTEXM3c=; b=OGMVOZ80M2bx+W3pgVpffTL38ANyuBXm1LwU5jqWgjR9GGp7Of9c3a12SrbeF6vryv ULw/m7xtOw99fgH96WfL9+v3BGdIarko+230kxyBkOuHQA6vVdTnaNe0xly//SdNajyY iYmCnsOIKb/XxXWSjx/k6HxPC3gVXmoqKq/5Ne7PJEQVgYW1XhEgTN8y6syeh3JJVbqr ONHShHswBHUUh8eysSWqyW91eTUWIWguZhc21QhG+hAZGJNlYJgtBvNxZOTofsOniWRw YEaGrnwsCEnhEfF2qU5P3WUjOcRahAxhwRom+ttr6MKUQM6Jx2wLrTQJD5CEL7FHiFf/ 1Btw== X-Gm-Message-State: AOPr4FWMIeFQ6PRFrLEX5lvH3Gtfw3rLO0JUb+/+/EN8AeuxTKEJubEF0k8odBwTNUsuJPBw03Lr6E4CICnQyA== MIME-Version: 1.0 X-Received: by 10.107.40.9 with SMTP id o9mr23059108ioo.183.1460748171301; Fri, 15 Apr 2016 12:22:51 -0700 (PDT) Sender: wlosh@bsdimp.com Received: by 10.79.104.197 with HTTP; Fri, 15 Apr 2016 12:22:51 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: <571129AD.6070106@gmx.de> References: <571129AD.6070106@gmx.de> Date: Fri, 15 Apr 2016 13:22:51 -0600 X-Google-Sender-Auth: 1pCQcyx2y99fN8uO3nx3ZNgE6Pg Message-ID: Subject: Re: Heads up From: Warner Losh To: FreeBSD Current Cc: Warren Block Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2016 19:22:52 -0000 On Fri, Apr 15, 2016 at 11:49 AM, olli hauer wrote: > On 2016-04-15 06:19, Warner Losh wrote: > > On Thu, Apr 14, 2016 at 9:56 PM, Warren Block > wrote: > > > >> On Thu, 14 Apr 2016, Warner Losh wrote: > >> > >> The CAM I/O scheduler has been committed to current. This work is > described > >>> in https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf though > the > >>> default scheduler doesn't change the default (old) behavior. > >>> > >>> One possible issue, however, is that it also enables NCQ Trims on ada > >>> SSDs. > >>> There are a few rogue drives that claim support for this feature, but > >>> actually implement data corrupt instead of queued trims. The list of > known > >>> rogues is believed to be complete, but some caution is in order. > >> > >> > > > >> Is the list of drives queryable? Is there an easy way to tell if the > >> currently-connected drives are on the list? > >> > > > > /usr/src/sys/cam/ata/ata_da.c has the list. > > > > dmesg will tell you if it detected a bad one since it prints the drive's > > quirks. > > But that's no big deal, because the bad one work just fine if you never > > issue > > a NCQ TRIM. This small group of drives were early adapters of this > > technology > > > > Here's the full list of known rogues: > > > > Crucial/Micron M500 (all firmware prior to MU07) > > Micron M510 MU01 firmware (newer firmware is good) > > Crucial/Micron M550 MU01 firmware (newer firmware is good) > > Crucial MX100 MU01 firmware (newer firmware is good) > > FCCT M500 all firmware > > Samsung 830 all firmware > > Samsung 840 all firmware > > Samsung 850 all firmware > > > > All of these are at least 18 months old (if not older). There's some > > confusing in Linux lists on > > the full impact of the Samsung drives (there was a bug in the Linux > > implementation (that can't > > be present in the FreeBSD implementation) that may have been the root > cause > > for the Samsung > > black listing). Out of an abundance of caution, I've kept them in the > list. > > Also, it's my belief that > > the Crucial/Micron models with MU01 firmware were mostly corrected after > > early samples > > since most of the channel drives I've helped people debug had MU02 > > firmware. Also, a quick > > google search shows the MU02 firmware for each of these models has been > > available for > > at least a year. > > > > Warner > > I suspect this was the reason why Samsung SSD's are listed on the Linux > blacklist. > https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/ > > But the article also reports it was a Linux kernel issue ... > >