From: David Weber <wb@munzinger.de>
To: linux-btrfs@vger.kernel.org
Subject: WARNING: at /fs/btrfs/extent-tree.c:4029 btrfs_free_reserved_data_space
Date: Mon, 29 Jun 2015 11:35:12 +0200 [thread overview]
Message-ID: <6617728.KSCQs1dauk@o3-3> (raw)
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?
Cheers,
David
next reply other threads:[~2015-06-29 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 9:35 David Weber [this message]
2015-06-29 10:37 ` WARNING: at /fs/btrfs/extent-tree.c:4029 btrfs_free_reserved_data_space Lutz Vieweg
2015-06-30 9:10 ` David Weber
2015-07-01 12:35 ` Lutz Vieweg
2015-07-07 12:28 ` David Weber
2015-07-07 14:45 ` Lutz Vieweg
2015-07-08 2:45 ` Liu Bo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6617728.KSCQs1dauk@o3-3 \
--to=wb@munzinger.de \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).