From: Lutz Vieweg <lvml@5t9.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: WARNING: at /fs/btrfs/extent-tree.c:4029 btrfs_free_reserved_data_space
Date: Mon, 29 Jun 2015 12:37:33 +0200 [thread overview]
Message-ID: <mmr75d$vbi$1@ger.gmane.org> (raw)
In-Reply-To: <6617728.KSCQs1dauk@o3-3>
On 06/29/2015 11:35 AM, David Weber wrote:
> we are testing Btrfs as a kvm storage system with
> "defaults,space_cache,nodatacow" mount options and regular snapshots.
That sounds brave - even with "nodatacow" it appeared to me
that using btrfs with often partially overwritten files like
VM images results in excessively fragmented files.
And taking snapshots kind of counteracts "nodatacow".
What does "filefrag" tell about your VM images on btrfs?
(As much as I like btrfs for other purposes, I currently stay
with XFS for VM images, database files and alike.)
Regards,
Lutz Vieweg
next prev parent reply other threads:[~2015-06-29 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 9:35 WARNING: at /fs/btrfs/extent-tree.c:4029 btrfs_free_reserved_data_space David Weber
2015-06-29 10:37 ` Lutz Vieweg [this message]
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='mmr75d$vbi$1@ger.gmane.org' \
--to=lvml@5t9.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).