Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS cache problem
Date: Sun, 11 Nov 2012 15:20:06 +0000	[thread overview]
Message-ID: <20121111152006.GA5604@carfax.org.uk> (raw)
In-Reply-To: <509ED1D6.8010903@petaramesh.org>

[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]

On Sat, Nov 10, 2012 at 11:14:46PM +0100, Swâmi Petaramesh wrote:
> Hi,
> 
> My BTRFS is mounted with space_cache,inode_cache , and I now get at boot
> time the following message :
> 
> “btrfs: free space inode generation (0) did not match free space cache
> generation (189086)”
> 
> Starting once with "clear_cache" doesn't seem to be able to fix the
> issue... Any clue ?

   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.

-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
         --- Great oxymorons of the world, no. 8: The Latest ---         
                          In Proven Technology                           

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  parent reply	other threads:[~2012-11-11 15:20 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 [this message]
2012-11-11 15:28   ` Swâmi Petaramesh
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=20121111152006.GA5604@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=swami@petaramesh.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox