On Fri, Jan 28, 2011 at 10:59:56AM +0100, Tomasz Chmielewski wrote: > Not sure if the: > > btrfs: free space inode generation (0) did not match free space cache generation > > is supposed to be fixed in 2.6.38-rc2? > It's not a problem, it just means that the cache is being discarded, which is what is supposed to happen. You probably ran out of space or one of the other corner cases where we can't write out the space cache. 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
