Date: Wed, 9 Sep 2015 11:17:18 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Jan Bramkamp <crest@rlwinm.de> Cc: freebsd-fs@freebsd.org Subject: Re: TRIM support (same bug as linux?) Message-ID: <alpine.BSF.2.20.1509091108440.83897@wonkity.com> In-Reply-To: <55F00CC4.7060600@rlwinm.de> References: <CAD=tpedAx2XLtQe6Nn%2BHvXWZ0X=TekmkpTruxCndYqpBXPFaFA@mail.gmail.com> <55F00CC4.7060600@rlwinm.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 9 Sep 2015, Jan Bramkamp wrote: > 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. They have test code to duplicate the bug here: https://github.com/algolia/trimtester The trim_periodic.sh script uses fstrim, a Linux command that "is used on a mounted filesystem to discard (or "trim") blocks which are not in use by the filesystem." In a batch. No idea how often that is used in real life.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1509091108440.83897>