All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Chester <somethingsome2000@gmail.com>
Cc: Miguel Garrido <miguel@mjgar.com>, Josef Bacik <josef@redhat.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: What are thoses [btrfs-cache-nnn] kernel threads ?
Date: Fri, 20 May 2011 07:22:03 -0400	[thread overview]
Message-ID: <1305890412-sup-1052@shiny> (raw)
In-Reply-To: <BANLkTimRPE-roV8JaRhQpqQW_sMtsW7Gww@mail.gmail.com>

Excerpts from Chester's message of 2011-05-20 01:32:22 -0400:
> >
> > Out of curiosity, why isn't this done automatically as opposed to
> > having to mount with the space_cache option?
> 
> The space_cache option changes the disk format. Once enabled, it will
> be permanent. The mount option gives people an option of whether they
> want to enable space_cache.. I've been using it, and it's pretty safe
> to use.

Once enabled it does stay on, and strictly speaking it does change the
disk format.  But, it is perfectly safe to go back to a non-space_cache
enabled kernel and then go back into space cache.  Josef set things up
so it would detect a non-space_cache mount and continue properly.

space_cache is wonderful.  We did fix up a few bugs in .38 and .39 but
I'll probably have .40 enable it by default.

-chris

  reply	other threads:[~2011-05-20 11:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19  2:37 What are thoses [btrfs-cache-nnn] kernel threads ? Christian Robert
2011-05-19 18:26 ` Josef Bacik
2011-05-20  3:13   ` Miguel Garrido
2011-05-20  5:32     ` Chester
2011-05-20 11:22       ` Chris Mason [this message]
2011-05-20 12:11         ` Miguel Garrido

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1305890412-sup-1052@shiny \
    --to=chris.mason@oracle.com \
    --cc=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=miguel@mjgar.com \
    --cc=somethingsome2000@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.