On 08/08/2011 08:17 AM, Andrew Lutomirski wrote: > On Mon, Aug 8, 2011 at 8:14 AM, Josef Bacik <josef@xxxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
