Date: Sat, 16 Apr 2016 10:52:41 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Warner Losh <imp@bsdimp.com> Cc: Warren Block <wblock@wonkity.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Heads up Message-ID: <20160416105241.338cdda0.ohartman@zedat.fu-berlin.de> In-Reply-To: <CANCZdfrPu9Z4aC34Nsm9%2BbGh86Gn8vuaez84w=xWfjNjxu=ZwA@mail.gmail.com> References: <CANCZdfpnYnVrvhNagYUT9RhAuC1AMCrxh=GCt8RKT0bqxuJybw@mail.gmail.com> <alpine.BSF.2.20.1604142154240.8359@wonkity.com> <CANCZdfqEWDLrHndKf8ZND1mM7spK9cq%2BnfnA79EVEaSj-MJfFA@mail.gmail.com> <20160415155143.0faa8204@freyja.zeit4.iv.bundesimmobilien.de> <CANCZdfrPu9Z4aC34Nsm9%2BbGh86Gn8vuaez84w=xWfjNjxu=ZwA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_//TnZ0kCVtjM+8u1_uw/bRrr Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Fri, 15 Apr 2016 08:26:23 -0600 Warner Losh <imp@bsdimp.com> schrieb: > On Fri, Apr 15, 2016 at 7:51 AM, O. Hartmann <ohartman@zedat.fu-berlin.de> > wrote: >=20 > > On Thu, 14 Apr 2016 22:19:23 -0600 > > Warner Losh <imp@bsdimp.com> wrote: > > =20 > > > On Thu, Apr 14, 2016 at 9:56 PM, Warren Block <wblock@wonkity.com> =20 > > wrote: =20 > > > =20 > > > > On Thu, 14 Apr 2016, Warner Losh wrote: > > > > > > > > The CAM I/O scheduler has been committed to current. This work is > > > > described =20 > > > >> in https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf thoug= h =20 > > the =20 > > > >> 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 =20 > > known =20 > > > >> rogues is believed to be complete, but some caution is in order. = =20 > > > > > > > > =20 > > > =20 > > > > Is the list of drives queryable? Is there an easy way to tell if t= he > > > > currently-connected drives are on the list? > > > > =20 > > > > > > /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 driv= e's > > > quirks. > > > But that's no big deal, because the bad one work just fine if you nev= er > > > 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 =20 > > > > 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). > > =20 >=20 > Which Micron drives? I'm not familiar with the 'Fujitsu' model for that > line. The boxes are Celsius M-7XX series boxes, I checked but forgot, but I think= its M600 type SSDs (sold with workstations Marsch/April 2015). > The newer ones are fine, the ones listed above with the MU01 firmware > being bad have MU02 firmware (or newer) available that fixes the problem. > The M500's firmware exists, but I don't know how available it is. So for > Micron, solutions to the problem exist. >=20 > The 830 and 840 apparently claim support, but are in the class of drives > that simply fail to actually work in what may be a reasonable way to dete= ct. > There's code to do the fallback in there now, but I'm not so sure that it= is > working given some of the reports I've seen. Maybe I need to try to but > a couple of these drives to see. I was mistaken, I personally use some 830 and since a couple of weeks 850 (= not 840). Both are marked as you described. >=20 > So - they are the most popular/used drives in a more "professional" > > environment these days and they get blacklisted :-( > > =20 >=20 > At least for the micron drives, you don't want to use NCQ trim on the > versions listed. It's data corruption roulette. For newer drives, it is > fine. > The performance will certainly be no worse than it was before my > commit. >=20 > 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" --Sig_//TnZ0kCVtjM+8u1_uw/bRrr Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXEf1ZAAoJEOgBcD7A/5N8qr8IALXu2c/QTDJkYFK3/o47+V9r t6Dk/mE5qFn2f6JEQ9tfoG5L60pVr07sfP36pi/363w6wQsGuSxoZB79DngNZey4 HI2qV9rCF+RqreXSaB+6ZR0aoefpnEprqbWSCKnsVvhxdoADS7H2QAhkJNa+LRSQ HGkqDpQ4j9VBVx8tsKnK16u3xkHY6mt4OcM5Uf900507g7em/qXxiJTVDS2YhljQ 5THIZqdnXnNxlmabgsfdM2nvKZzDBVmXyPmSdy3LFc13hWlSPkvwpuOT16vEKdeB Z2h/4/Czua8b9Pdo/7b7qgrKWvVZyJKdrCoRHm4kvQhxzu4+pEqq56MOmIuBbSs= =Y51p -----END PGP SIGNATURE----- --Sig_//TnZ0kCVtjM+8u1_uw/bRrr--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160416105241.338cdda0.ohartman>