On Mon, Jun 29, 2015 at 11:35:12AM +0200, David Weber wrote: > Hi, > > we are testing Btrfs as a kvm storage system with > "defaults,space_cache,nodatacow" mount options and regular snapshots. While > testing we sometimes get these warnings: > WARNING: CPU: 5 PID: 11335 at /home/kernel/COD/linux/fs/btrfs/extent- > tree.c:4029 btrfs_free_reserved_data_space+0x102/0x110 [btrfs]() > > Full log: > https://gist.github.com/anonymous/5f672f72899a3d52c20c > > Once they start, they flood dmesg with several messages per second. After a > reboot, it takes a while until they start to appear again. > We have seen them with Linux 4.0.6 and 4.1 > > This was already reported a few times: > https://bugzilla.opensuse.org/show_bug.cgi?id=904023 > https://bugzilla.redhat.com/show_bug.cgi?id=1173937 > http://www.spinics.net/lists/linux-btrfs/msg39069.html > https://lkml.org/lkml/2014/10/22/899 > > Always with no solution > Is this a real problem or can we safely ignore this?
Didn't notice this mail but it looks like thia patch is promising to fix your issue, worth giving a shot. https://patchwork.kernel.org/patch/6623001/ Btrfs: fix warning of bytes_may_use BTW, this's been queued for the next merge, so you can try the latest btrfs from integration-4.2 of the offical btrfs repo[1]. [1]: https://git.kernel.org/cgit/linux/kernel/git/mason/linux-btrfs.git Thanks, -liubo > > Cheers, > David > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
