From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ie0-f182.google.com ([209.85.223.182]:42590 "EHLO mail-ie0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754183Ab3EZRGW (ORCPT ); Sun, 26 May 2013 13:06:22 -0400 Received: by mail-ie0-f182.google.com with SMTP id a14so16788797iee.27 for ; Sun, 26 May 2013 10:06:22 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <1751895.r3q1HmeO0C@merkaba> Date: Sun, 26 May 2013 11:06:22 -0600 Message-ID: Subject: Re: Recommended settings for SSD From: cwillu To: Harald Glatt Cc: Leonidas Spyropoulos , Martin Steigerwald , Duncan <1i5t5.duncan@cox.net>, "linux-btrfs@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Sun, May 26, 2013 at 9:16 AM, Harald Glatt wrote: > I don't know a better way to check than doing df -h before and > after... If you use space_cache you have to clear_cache though to make > the numbers be current for sure each time before looking at df. Not sure what you're thinking of; space_cache is just a mount-time optimization, storing and loading a memory structure to disk so that it doesn't have to be regenerated. As I understand it, if it's ever wrong, it's a serious bug.