From owner-freebsd-current@freebsd.org Fri Apr 15 13:51:53 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 7A0ADAED9AA for ; Fri, 15 Apr 2016 13:51:53 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3C0DF1C68 for ; Fri, 15 Apr 2016 13:51:53 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1ar4A2-001Y3S-Ch>; Fri, 15 Apr 2016 15:51:50 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (envelope-from ) id <1ar4A2-0042vo-2Y>; Fri, 15 Apr 2016 15:51:50 +0200 Date: Fri, 15 Apr 2016 15:51:43 +0200 From: "O. Hartmann" To: Warner Losh Cc: Warren Block , FreeBSD Current Subject: Re: Heads up Message-ID: <20160415155143.0faa8204@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: References: Organization: FU Berlin X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 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 13:51:53 -0000 On Thu, 14 Apr 2016 22:19:23 -0600 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 This is funny, ALL of our Fujitsu Workstations and those I use pprivate do have Micron SSD drives (Fujitsu) and Samsung SSD (830 and 840). So - they are the most popular/used drives in a more "professional" environment these days and they get blacklisted :-( > > 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 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"