From owner-freebsd-current@freebsd.org Fri Apr 15 17:44:59 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 F080CAEDBAB for ; Fri, 15 Apr 2016 17:44:59 +0000 (UTC) (envelope-from ohauer@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B1A91450 for ; Fri, 15 Apr 2016 17:44:58 +0000 (UTC) (envelope-from ohauer@gmx.de) Received: from [192.168.100.100] ([87.139.233.65]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0M5tzh-1bff7R1ns9-00xsTz; Fri, 15 Apr 2016 19:44:32 +0200 Subject: Re: Heads up To: FreeBSD Current References: Reply-To: FreeBSD Current Cc: Warner Losh , Warren Block From: olli hauer Message-ID: <571129AD.6070106@gmx.de> Date: Fri, 15 Apr 2016 19:49:33 +0200 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:q8VgMS4Kzgfk9nWmIjSEPPOvmi23/6YSg3iGJsOAtAVc3XWOXz1 knHbolqN3EZWPbsat6dHwo+7yyZR0hPRdG7s+LbmSA+RhTWgQDchhIfRwn2F1ETC6dFVpUr K6HpFSpPqaLGyTjCtYoS5fLtd1YlAi36Re8xmJPDcGVLA6yRvTkTtTyi5QZbtMmwCA/yKT+ HS0rvl95dRmOgGP+Bsbiw== X-UI-Out-Filterresults: notjunk:1;V01:K0:Hoyu+gEVT2Q=:4J+ClrpgfEghMpG0ksrsWI 09qcqCklscFIuxl1BXFXNQG6yubzb43tpKqOy+OldydM2vhM1xRVD4cadT3inKQyVK2iQOkYo uEQ1Fyh46WLcc3SRCd1cZs1DYudwjpxdWahNxFQgNdxRmTURp71r0Sde9vmzBitNZm4xbgY47 3lgEHpDXDuA3BxPdKNT7FM4i85FiE5Aj2IRbb220vzW+4CPAIRo6Kg/1dSnm42/DZdRk8yKrW 8Ti9Ysbfv5SfzYhMn/BwtqYYRCK7VrL2qAQJBT8Djx0KJq+JTvY5upcqqEFSQqYh+abPx7hTN SqFvYRfITw0yoXBHl+0y74elkziO9TWcjzOPeqryfD60oTFQr78XLjNRqFzjQFDt2tomJhaOD aWk7effolnnMRN9kV2ggBIl5OO/4TsVBJpecFf7R2R+jeo6Tl9RwYxjR0Y8JYlaQr/DI5CdDi kRy19iaXNLHe+JAkLXHToxjfWfo4sFoEucoKZA9mQxqd/qfZ/GN9SJmwv+AsaN8D+kwYXOtfA DWY2SMjLvjT30zhOH1XzNqXqQy4/E99/HqmMDlKDq10D4ESNVCZ5YX3VGnRJaDsCG46xnpROb bKsr8BYwYk9MltRtGtB3WwquabFJDdtgT3W9C27NBTrb4QVWDxCteVqDBuv9liS1rihqRIqrS IsxxzHBcvR6I8Iam2VkPkH3jlnj6c6xGdPVht7T/4PiqkdNy+OUtE73Ygcz5jJ1ULCWTCJKP7 Ibg76Szv4rEcq+jsi00IU14HFXb0uUf9GiXBLBaOuoaLzWImlDQ37Vk7Rzo8K0P4hxR08NuFf 4m0s0OE 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 17:45:00 -0000 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 ...