From owner-freebsd-fs@freebsd.org Wed Sep 9 01:42:29 2015 Return-Path: Delivered-To: freebsd-fs@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 598129CD318 for ; Wed, 9 Sep 2015 01:42:29 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from mail-qg0-x236.google.com (mail-qg0-x236.google.com [IPv6:2607:f8b0:400d:c04::236]) (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 11C281F2E for ; Wed, 9 Sep 2015 01:42:29 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: by qgev79 with SMTP id v79so98830885qge.0 for ; Tue, 08 Sep 2015 18:42:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type; bh=ooIYsWVFf8UEm3qIq6pkx2WmiBJrvtHRCggxRIznGd8=; b=bSUg6HLqeB6yvIgbzFR4nL0FBQ8ta1EJ4w9EmbIWtcRl6i8KEk6Y3Zi0chEn6CitIH 19+frkVpimzHb3Tp64JaHKqh5Hi+ch5qVpvKXzjpWd8lkNtijTg5sQmVWydcnCik3zYC +b/c1PkvrTT90iFjXR7/36I3N1/1oZnABVwkCdGGf/Ri/4Rqid/UjYX0MY92qy95u6jV Xr7SKsLrG+maWU0/dwLxe0Kz1fydWeMkA4PFtGG1iKUH+kVX/HkBsc5upErb1BObkvKA 5eUTyT7fkU+ZZ9V2NV34C2JNkOLmDAIwXuvHNXcAxgBaLko5ByM45fnXfbZXUY2Zs0nr 8QwA== X-Received: by 10.140.150.139 with SMTP id 133mr43151487qhw.58.1441762948059; Tue, 08 Sep 2015 18:42:28 -0700 (PDT) Received: from kan ([2601:18f:0:1570:226:18ff:fe00:232e]) by smtp.gmail.com with ESMTPSA id s52sm2983604qge.19.2015.09.08.18.42.26 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 08 Sep 2015 18:42:26 -0700 (PDT) Date: Tue, 8 Sep 2015 21:42:21 -0400 From: Alexander Kabaev To: Tom Curry Cc: Mark Saad , "freebsd-fs@freebsd.org" Subject: Re: TRIM support (same bug as linux?) Message-ID: <20150908214221.7a1702e0@kan> In-Reply-To: References: <55EF7265.2050309@multiplay.co.uk> <1BCC8B97-6C79-4864-8405-BA687577808A@longcount.org> X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/Z_P.WkuqF3EOgH1ykpD7vRg"; protocol="application/pgp-signature" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Sep 2015 01:42:29 -0000 --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 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 > wrote: >=20 > > > > > > > On Sep 8, 2015, at 7:42 PM, Steven Hartland > > > > > 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--