Date: Tue, 8 Sep 2015 21:11:24 -0400 From: Mark Saad <nonesuch@longcount.org> To: Steven Hartland <killing@multiplay.co.uk> Cc: "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org> Subject: Re: TRIM support (same bug as linux?) Message-ID: <1BCC8B97-6C79-4864-8405-BA687577808A@longcount.org> In-Reply-To: <55EF7265.2050309@multiplay.co.uk> References: <CAD=tpedAx2XLtQe6Nn%2BHvXWZ0X=TekmkpTruxCndYqpBXPFaFA@mail.gmail.com> <55EF7265.2050309@multiplay.co.uk>
index | next in thread | previous in thread | raw e-mail
> 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 > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1BCC8B97-6C79-4864-8405-BA687577808A>