From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 4CAE413877A for ; Sat, 21 Jun 2014 14:54:18 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 037F4E085D; Sat, 21 Jun 2014 14:54:13 +0000 (UTC) Received: from mail-ve0-f172.google.com (mail-ve0-f172.google.com [209.85.128.172]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id EAACEE0831 for ; Sat, 21 Jun 2014 14:54:11 +0000 (UTC) Received: by mail-ve0-f172.google.com with SMTP id jz11so4649917veb.3 for ; Sat, 21 Jun 2014 07:54:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=wek2z/3xabG/i8McGR+0TQfyMIGaR41zGOTr+ig6AIg=; b=vy1gEaYmX+5RmOIEtGB6exQp+RYGDQsS8BCq3Iv9rs1KpN37zlGFQ/J1YirTC8AUgK oVJf+ROOw7ahaTWLiSliuS6/8G3bKb8tLo7Q884jmWwSuu8tRTAWyqfvRVPiTV7JR4mf T4kKb+oF39z/qSkMZh4Mrc+YfsgeMdlpOWjaE4P8rmNiJKwuGfWcNs3BubRvS90gQ1QC 4IbFj32SiU+Odfdr1BYneR9ZaumlNmRg+vupwdztWqsNPki6I7nDow4FQRz1l4PfM7y+ XYXOlE71kU1TXIVExr34Jk6C+bp6317Zw3x0Ys5j6/YUPPXCr5Py4W61waoDuQZM03zj j+6w== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.58.1.228 with SMTP id 4mr186982vep.46.1403362450967; Sat, 21 Jun 2014 07:54:10 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.52.30.227 with HTTP; Sat, 21 Jun 2014 07:54:10 -0700 (PDT) In-Reply-To: <2770815.rPAQsmKHEU@wstn> References: <2770815.rPAQsmKHEU@wstn> Date: Sat, 21 Jun 2014 10:54:10 -0400 X-Google-Sender-Auth: pStjsWrZ9gMs3akPcdGzLSYQ9Ng Message-ID: Subject: Re: [gentoo-user] Re: [Gentoo-User] emerge --sync likely to kill SSD? From: Rich Freeman To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 29808749-a29d-4960-a3b4-3371818b9689 X-Archives-Hash: 6f5b6dc772603263379a1822064dd295 On Sat, Jun 21, 2014 at 10:27 AM, Peter Humphrey wrote: > > I found that fstrim can't work on f2fs file systems. I don't know whether > discard works yet. Fstrim is to be preferred over discard in general. However, I suspect neither is needed for something like f2fs. Being log-based it doesn't really overwrite data in place. I suspect that it waits until an entire region of the disk is unused and then it TRIMs the whole region. However, I haven't actually used it and only know the little I've read about it. That is the principle of a log-based filesystem. I'm running btrfs on my SSD root, which is supposed to be decent for flash, but the SMART attributes of my drive aren't well-documented so I couldn't tell you what the erase count is up to. Rich