From mboxrd@z Thu Jan 1 00:00:00 1970 From: Josef Bacik Subject: Re: space cache generation (...) does not match inode (...) Date: Mon, 08 Aug 2011 08:18:57 -0400 Message-ID: <4E3FD431.7070601@redhat.com> References: <4E3FD332.5020002@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: linux-btrfs To: Andrew Lutomirski Return-path: In-Reply-To: List-ID: On 08/08/2011 08:17 AM, Andrew Lutomirski wrote: > On Mon, Aug 8, 2011 at 8:14 AM, Josef Bacik wrote: >> 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, > > Can you put in a rate limit and make the message less alarming? > There's enough log spam from it that I can't see anything else in my > log. > Yeah I'll do that now, thanks, Josef