From owner-freebsd-current@freebsd.org Fri Apr 15 19:24:00 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 71F6CAEDDBE for ; Fri, 15 Apr 2016 19:24:00 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ig0-x241.google.com (mail-ig0-x241.google.com [IPv6:2607:f8b0:4001:c05::241]) (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 3AB371C92 for ; Fri, 15 Apr 2016 19:24:00 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ig0-x241.google.com with SMTP id g8so4080204igr.0 for ; Fri, 15 Apr 2016 12:24:00 -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=vByRukDZjoPeUxVS1o6Sz4JC863k5aNgbHMJV62KemM=; b=i/2Oy2fWYRvg9upav5nKI8yQJec+Y7zNTtvBLrRDKf/u8KifXApBIrLuAx5pAcxUIg 52JyaoKafUN0EdkpkujzLDrJFcSe68+OXwoEaQKtN6CrhkJ8Rj/KRRZQvF9DU+ddJwnQ X20B/B4QJ0R682cIu8v5MW9/rdSGKkW9RMBJ51LVhGxe6ibx3+fTwxiYRg770KMvJ0xQ Vi4OZQb4jbT5xxMjvlis/jhovrGg/siXS16dEigm2HDqtOTojJ32en72ekT8hdtgr4ry cG+RfiB6TafPD5n79Kr1rgCG+FYsFZroSx1EqhUSExgG5cGu+YZFqoI0Q46DArV5xznk 3mKg== 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=vByRukDZjoPeUxVS1o6Sz4JC863k5aNgbHMJV62KemM=; b=GdRjO2v5xPr3dr6qCSIPCO8rfAXQjU02oAFt8QLjEB9+Q//7gwPeZBNRjf9qda9Mf5 Wcf5G40pHB+NT7ebrFlC7SdkHDlPRq1JZn0TZkngdUmobzrwGJC8AZ5DgQIbgTMp5X/T 11rrTBF7uRbCSisWkavz94x/Hpzs4rbbSztb7Xw6Fq0eSc8/Uox7MuG/QZP+WP18K4G5 +49X1Y4gw8AI+TQgSNzxPEVcbAVsM3iQpIlivaM1LtkybqcGB8PtNACemiGG+XUzqcBZ 5yTZT4DzBT8fl6jfal7c3xIECWYdjcSBUMKlAxUyw+mwCWKBZ6q6th1S7n72cb+TAqZ7 4PfA== X-Gm-Message-State: AOPr4FXkno1iQnC+Pe2VaY9IJyjytlBRY3hq5vY2sIrNS1WasixEhpZUDVHgGeT4xje3x47sUaR34ZW/6YuRSg== MIME-Version: 1.0 X-Received: by 10.50.110.99 with SMTP id hz3mr6695515igb.16.1460748239688; Fri, 15 Apr 2016 12:23:59 -0700 (PDT) Sender: wlosh@bsdimp.com Received: by 10.79.104.197 with HTTP; Fri, 15 Apr 2016 12:23:59 -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:23:59 -0600 X-Google-Sender-Auth: UumuzpIq9C6iAlx2pp-_n1asb60 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:24:00 -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 .. > I've done a lot of research for this issue. There's two reasons they were listed. One was a Linux kernel bug. The other was that early drives reported that it was supported when, in fact, it wasn't. I've constrained the list to the latter. Warner