On Fri, Jan 28, 2011 at 02:56:24PM +0100, Tomasz Chmielewski wrote: > On 28.01.2011 14:45, Josef Bacik wrote: >> 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, > > FYI, there is plenty of free space (~150 GB). > > It could be some corner case: > > - filesystem is mounted with compress-force, > - one kvm process (the only writer to btrfs) writes to the btrfs > filesystem, via the virtual guest using a 220 GB qcow2 image file (lots > of writes) and a 7 GB qcow2 image file (very few writes). > I'll try some tests with compress-force to make sure it's not getting overly screwed, but this is just one of the drawbacks with the space cache stuff, sometimes we just can't write it out without deadlocking, so we err on the side of caution. 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
