From: Gert Menke <gert@menke.ac>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS as image store for KVM?
Date: Thu, 17 Sep 2015 23:32:56 +0200 [thread overview]
Message-ID: <55FB3188.2060909@menke.ac> (raw)
In-Reply-To: <CAJCQCtR_3eiWWmpJHC9RT4EJOzUb_AmrQkkm0X4R0OE4FYUHMQ@mail.gmail.com>
On 17.09.2015 at 20:35, Chris Murphy wrote:
> You can use Btrfs in the guest to get at least notification of SDC.
Yes, but I'd rather not depend on all potential guest OSes having btrfs
or something similar.
> Another way is to put a conventional fs image on e.g. GlusterFS with
> checksumming enabled (and at least distributed+replicated filtering).
This sounds interesting! I'll have a look at this.
> If you do this directly on Btrfs, maybe you can mitigate some of the
> fragmentation issues with bcache or dmcache;
Thanks, I did not know about these. bcache seems to be more or less what
"zpool add foo cache /dev/ssd" does. Definitely worth a look.
> and for persistent snapshotting, use qcow2 to do it instead of Btrfs.
You'd use Btrfs
> snapshots to create a subvolume for doing backups of the images, and
> then get rid of the Btrfs snapshot.
Good idea.
Thanks!
next prev parent reply other threads:[~2015-09-17 21:33 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 21:34 BTRFS as image store for KVM? Gert Menke
2015-09-16 3:00 ` Chris Murphy
2015-09-16 3:57 ` Duncan
2015-09-16 11:35 ` Brendan Heading
2015-09-16 12:25 ` Austin S Hemmelgarn
2015-09-16 12:41 ` Paul Jones
2015-09-17 17:56 ` Gert Menke
2015-09-17 18:35 ` Chris Murphy
2015-09-17 21:32 ` Gert Menke [this message]
2015-09-18 2:00 ` Duncan
2015-09-18 8:32 ` Gert Menke
2015-09-23 7:28 ` Russell Coker
2015-09-18 14:13 ` Austin S Hemmelgarn
2015-09-23 7:24 ` Russell Coker
2015-09-17 18:46 ` Mike Fleetwood
2015-09-17 19:43 ` Hugo Mills
2015-09-17 21:49 ` Gert Menke
2015-09-18 2:22 ` Duncan
2015-09-18 8:59 ` Gert Menke
2015-09-17 22:41 ` Sean Greenslade
2015-09-18 7:34 ` Gert Menke
2015-09-17 4:19 ` Paul Harvey
2015-09-20 1:26 ` Jim Salter
2015-09-25 12:48 ` Rich Freeman
2015-09-25 12:56 ` Jim Salter
2015-09-25 13:04 ` Austin S Hemmelgarn
[not found] ` <5605483A.7040103@jrs-s.net>
2015-09-25 13:46 ` Austin S Hemmelgarn
2015-09-25 13:52 ` Jim Salter
2015-09-25 14:02 ` Timofey Titovets
2015-09-25 14:20 ` Austin S Hemmelgarn
2015-09-29 14:12 ` Gert Menke
2015-10-02 4:21 ` Russell Coker
2015-10-02 12:07 ` Austin S Hemmelgarn
2015-10-03 8:32 ` Russell Coker
2015-10-04 2:09 ` Duncan
2015-10-04 12:03 ` Lionel Bouton
2015-10-04 12:21 ` Rich Freeman
2015-10-05 8:19 ` Duncan
2015-10-05 8:43 ` Erkki Seppala
2015-10-05 8:51 ` Roman Mamedov
2015-10-05 11:16 ` Lionel Bouton
2015-10-05 11:40 ` Rich Freeman
2015-10-05 11:54 ` Austin S Hemmelgarn
[not found] ` <RPG31r00t34oj7R01PG5Us>
2015-10-05 14:04 ` Duncan
2015-10-05 15:59 ` Austin S Hemmelgarn
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=55FB3188.2060909@menke.ac \
--to=gert@menke.ac \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).