All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: BTRFS cache problem
Date: Sun, 11 Nov 2012 16:28:54 +0100	[thread overview]
Message-ID: <509FC436.6080205@petaramesh.org> (raw)
In-Reply-To: <20121111152006.GA5604@carfax.org.uk>

Le 11/11/2012 16:20, Hugo Mills a écrit :
> You only need to mount with space_cache once, and after that it's
> "sticky". What's probably happening is that you're mounting with
> space_cache, which rebuilds the cache. Then, if you reboot before it's
> finished rebuilding the cache, the cache isn't complete, and (I think)
> it causes the above message -- which is harmless. The same applies to
> the inode cache options. Try mounting with clear_cache *once*, then
> remounting with space_cache,inode_cache *once*, and waiting for it to
> finish rebuilding the cache. Finally, remove all mention of the caches
> from your fstab and kernel command line before you next mount the FS.
> Hugo. 

Thanks very much Hugo, I'll give this a try. Should I assume that the
cache clearing / building is complete as soon as the disk is idle ?

-- 
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
Ne cherchez pas : Je ne suis pas sur Facebook.


  reply	other threads:[~2012-11-11 15:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-10 22:14 BTRFS cache problem Swâmi Petaramesh
2012-11-11 14:05 ` Bart Noordervliet
2012-11-11 14:13   ` Swâmi Petaramesh
     [not found]     ` <CAGy7UtgrdGpC5uav0m0yX1oJ47OR6WsX0vOtKu4p5umS4hZUtw@mail.gmail.com>
2012-11-11 14:26       ` Swâmi Petaramesh
2012-11-11 15:13         ` Bart Noordervliet
2012-11-11 16:02           ` Swâmi Petaramesh
2012-11-11 15:20 ` Hugo Mills
2012-11-11 15:28   ` Swâmi Petaramesh [this message]
2012-11-11 15:37     ` Hugo Mills
2012-11-11 16:21   ` Swâmi Petaramesh

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=509FC436.6080205@petaramesh.org \
    --to=swami@petaramesh.org \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    /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.