Date: Tue, 8 Sep 2015 21:42:21 -0400 From: Alexander Kabaev <kabaev@gmail.com> To: Tom Curry <thomasrcurry@gmail.com> Cc: Mark Saad <nonesuch@longcount.org>, "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: TRIM support (same bug as linux?) Message-ID: <20150908214221.7a1702e0@kan> In-Reply-To: <CAGtEZUBgbufc2W%2BiFg_7XVWyF4_mcfd8mj1=UMyTHM-RCWWR_g@mail.gmail.com> References: <CAD=tpedAx2XLtQe6Nn%2BHvXWZ0X=TekmkpTruxCndYqpBXPFaFA@mail.gmail.com> <55EF7265.2050309@multiplay.co.uk> <1BCC8B97-6C79-4864-8405-BA687577808A@longcount.org> <CAGtEZUBgbufc2W%2BiFg_7XVWyF4_mcfd8mj1=UMyTHM-RCWWR_g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/Z_P.WkuqF3EOgH1ykpD7vRg Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 8 Sep 2015 21:28:01 -0400 Tom Curry <thomasrcurry@gmail.com> wrote: > I'm no expert but if memory serves the issue had to do with concurrent > and/or queued trim which is not implemented in FreeBSD. >=20 > On Tue, Sep 8, 2015 at 9:11 PM, Mark Saad <nonesuch@longcount.org> > wrote: >=20 > > > > > > > On Sep 8, 2015, at 7:42 PM, Steven Hartland > > > <killing@multiplay.co.uk> > > wrote: > > > > > > Nope FreeBSD is not affected by this. > > > > > >> On 09/09/2015 00:15, FF wrote: > > >> I'm asking a pretty vague question and I apologize in advance, > > >> not > > trying > > >> to troll. > > >> > > >> The question has to do with whether FreeBSD is using TRIM the > > >> same way > > as > > >> recent Linux kernels. > > >> > > >> https://blog.algolia.com/when-solid-state-drives-are-not-that-solid/ > > seems > > >> to imply that there are instabilities that can occur. Trying to > > >> avoid duplicating effort if this has already been addressed or > > >> if its a > > complete > > >> dead alley because there isn't a commonality. > > >> > > >> Thanks in advance! > > > > > > > It would be interesting if anyone could explain the reasons why > > ufs/ffs and zfs and FreeBSD are not effected by this issue . My > > rudimentary understanding of the issue was that it's wasn't just a > > software glitch in the ext filesystem and bad firmware but a > > combination of that and Linux poorly supporting a ata modes that > > are not supported at all on FreeBSD . Is that correct ? > > > > > > --- > > Mark Saad | nonesuch@longcount.org Wasn't the root cause the improper bio splitting code in md/raid0 code and nothing special in firmware? FreeBSD shares no such code and as such is not affected. --=20 Alexander Kabaev --Sig_/Z_P.WkuqF3EOgH1ykpD7vRg Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJV7459XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDNUY3RDk5NTk5QjY0MUUxM0M1MTU2OTEw NzEzMjI5OTkyNzkyRTdFAAoJEAcTIpmSeS5+NacQAKygqqyAOdTvbQUQ3EaVTGC2 GK8OzzgBqvG1oXQmNZj95Dd5tEBwWbLfq4A48eFDKcFlmdjC/ldVTYlG4GrYiiml c8h9UarrLA9nhjVFBCYep4iRT8/jS13Xq0ejmZETltrjoEssLLbIhO4oQaXebGwB qWlKUunWkMtO5akJ2ryoNTuBCKHPnHMhRF6U4rTtAZvooMizz3DuqerD0CD7PIov tRRxwN1KTGyZfBRxfApAIfyQoSWIOTP3QxyZFZ0M+wqz7YDqPQSZUsivnY4YExUp se/iFLR/ltYD7UKl3wE5l93pc7Ly/xWLb8/w56gwZApIuTzmPTM6AzvH2D3WJ34/ PWfq3O2v8oFN+0MTULjU6/m9RbDn3QLGmiMob6/IFp17ANRP70+glhK/W8EDmsNj jnMt8QwDTKqkCcruWLUr8/zsyQdeQJB8O2TdhCzs99foeyqHa2wvfjPYWqgNJLvm V1KX2g1bGv23h3UGOIR4wRR6sFTXkPPkDOOqP25WrJSkkjAkDgekSUHcIRCbJnsZ /KFND6xT6kvPRMx6MJBP0/pvZQOvaLCO9xPWzwk+CDBZQoFS39EaXOzXrw5O6CR1 DU4voYLwRHEVE4RI28VILzr65v8ZgDSjJMBcSnhT6Vw21i5dvrVmZwCZF4Ehtqcl ezzxVDJnv0LHt6pVZH4r =nkda -----END PGP SIGNATURE----- --Sig_/Z_P.WkuqF3EOgH1ykpD7vRg--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150908214221.7a1702e0>