From owner-freebsd-fs@freebsd.org Wed Sep 9 01:28:02 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 AE7C4A00BBB for ; Wed, 9 Sep 2015 01:28:02 +0000 (UTC) (envelope-from thomasrcurry@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 790EE17AB for ; Wed, 9 Sep 2015 01:28:02 +0000 (UTC) (envelope-from thomasrcurry@gmail.com) Received: by iofh134 with SMTP id h134so5512875iof.0 for ; Tue, 08 Sep 2015 18:28:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9Bpm+Lv9ZANPcU2YjS/plCzyR4jOeTsTOgRGjry5QP8=; b=x7e8z/wKO152pWIZAXChYZa/ZQW0nIvxy6ctrGpmTWyXayet2SnVi4iEDCvyYRb/8s bX09JgE0Hor/clOG+2VXE7MfC9yolGye8OcCbslQvbhFsQa+ggWvIt9dc9SrNhLiHVTF IhAIFxBUY6hDEpyfHmuY1pGtpmbwnt6amYPUHPn2LIarA4MD+3S9F0+M0mLhgLfYASR7 5q6eOpTOFEL7MlXJKs73vLR1O5z8MzPULaDR2qHv+oCBpNKJ/BGm1WAeccbsoIau9F4U QeuWJhD1wvCg5Q0ib6MXMRgrjSzS99UmIAQBaYLoCiduxWRImaiCUhMC7ckQmsc9QaS0 qQaQ== MIME-Version: 1.0 X-Received: by 10.107.10.165 with SMTP id 37mr45278657iok.120.1441762081815; Tue, 08 Sep 2015 18:28:01 -0700 (PDT) Received: by 10.107.4.72 with HTTP; Tue, 8 Sep 2015 18:28:01 -0700 (PDT) In-Reply-To: <1BCC8B97-6C79-4864-8405-BA687577808A@longcount.org> References: <55EF7265.2050309@multiplay.co.uk> <1BCC8B97-6C79-4864-8405-BA687577808A@longcount.org> Date: Tue, 8 Sep 2015 21:28:01 -0400 Message-ID: Subject: Re: TRIM support (same bug as linux?) From: Tom Curry To: Mark Saad Cc: Steven Hartland , "freebsd-fs@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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:28:02 -0000 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. On Tue, Sep 8, 2015 at 9:11 PM, Mark Saad wrote: > > > > 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 > > _______________________________________________ > > 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" > _______________________________________________ > 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" >