From: Josef Bacik <josef@redhat.com>
To: Andrew Lutomirski <luto@mit.edu>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: space cache generation (...) does not match inode (...)
Date: Mon, 08 Aug 2011 08:14:42 -0400 [thread overview]
Message-ID: <4E3FD332.5020002@redhat.com> (raw)
In-Reply-To: <CAObL_7Hc0AGOB8Jk-o_hseiqxEfDWFLSnMkhLLiu00GVbr729Q@mail.gmail.com>
On 08/06/2011 10:16 PM, Andrew Lutomirski wrote:
> I've always gotten space cache generation warnings, but some time
> after 3.0 they started going nuts. I get:
>
> space cache generation (14667727114112179905) does not match inode (154185)
>
> and other similar messages (with a huge number and a smaller number)
> at rates higher than one message per ms. They don't happen
> constantly, but they come in bursts big enough to fill my log buffer.
>
Yeah sorry that's going to happen when you first switch to 3.0. We
switched the space cache stuff over to using the normal checksumming
code so all old space cache is going to look invalid. This is nothing
to worry about, it will just end up discarded and re-generated. Thanks,
Josef
next prev parent reply other threads:[~2011-08-08 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 2:16 space cache generation (...) does not match inode (...) Andrew Lutomirski
2011-08-08 12:14 ` Josef Bacik [this message]
2011-08-08 12:17 ` Andrew Lutomirski
2011-08-08 12:18 ` Josef Bacik
2011-11-07 9:37 ` Martin Steigerwald
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=4E3FD332.5020002@redhat.com \
--to=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=luto@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).