From owner-freebsd-fs@freebsd.org Wed Sep 9 10:41:12 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 A685BA00C65 for ; Wed, 9 Sep 2015 10:41:12 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from smtp.rlwinm.de (smtp.rlwinm.de [IPv6:2a01:4f8:201:31ef::e]) (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 6F25B1914 for ; Wed, 9 Sep 2015 10:41:12 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from crest.local (unknown [87.253.189.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.rlwinm.de (Postfix) with ESMTPSA id 506966D7A for ; Wed, 9 Sep 2015 12:41:09 +0200 (CEST) Subject: Re: TRIM support (same bug as linux?) To: freebsd-fs@freebsd.org References: From: Jan Bramkamp Message-ID: <55F00CC4.7060600@rlwinm.de> Date: Wed, 9 Sep 2015 12:41:08 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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 10:41:12 -0000 On 09/09/15 01: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. At first the leading theory was that Linux triggered a firmware bug in the SSDs or that a bug in the handling of queued TRIM operations is responsible. The real culprit was a bug in the code for linear mdraid volumes causing the wrong blocks to be unmapped with TRIM.