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: Tue, 07 Jul 2015 16:45:10 +0200 [thread overview]
Message-ID: <mngolm$9q$1@ger.gmane.org> (raw)
In-Reply-To: <loom.20150707T142359-534@post.gmane.org>
On 07/07/2015 02:28 PM, David Weber wrote:
>> How do you backup the VM images? If filefrag takes hours to complete,
>> I'd assume that attempting a sequential read of the whole file (from a
>> backup software) takes just as long.
>
> I use send/receive. With an SSD it doesn't take that long.
Hmmm. The kind of backup you can restore only as a whole,
not individual files... plus you have to hope there are never
systematic bugs in btrfs that would make an individual file
as unreadable from the backup (undetected by send/receive)
as it is from the original. :-)
I for one prefer backups to read/write individual files and
to use a different format for storage.
> A sequential read (dd if=Windows7.vdi of=/dev/zero bs=1M) gives nearly raw
> SSD Speed. But CPU consumption is indeed quite high...
Ok, if all the VM image data is on SSDs, the high fragmentation
might be less of an issue to you.
Regards,
Lutz Vieweg
next prev parent reply other threads:[~2015-07-07 14:45 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
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 [this message]
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='mngolm$9q$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).