From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS as image store for KVM?
Date: Fri, 18 Sep 2015 02:00:15 +0000 (UTC) [thread overview]
Message-ID: <pan$270e2$4b4f9ec6$a323af50$ada695ce@cox.net> (raw)
In-Reply-To: CAJCQCtR_3eiWWmpJHC9RT4EJOzUb_AmrQkkm0X4R0OE4FYUHMQ@mail.gmail.com
Chris Murphy posted on Thu, 17 Sep 2015 12:35:41 -0600 as excerpted:
> You'd use Btrfs snapshots to create a subvolume for doing backups of
> the images, and then get rid of the Btrfs snapshot.
The caveat here is that if the VM/DB is active during the backups (btrfs
send/receive or other), it'll still COW1 any writes during the existence
of the btrfs snapshot. If the backup can be scheduled during VM/DB
downtime or at least when activity is very low, the relatively short COW1
time should avoid serious fragmentation, but if not, even only relatively
temporary snapshots are likely to trigger noticeable cow1 fragmentation
issues eventually.
Some users have ameliorated that by scheduling weekly or monthly btrfs
defrag, reporting that cow1 issues with temporary snapshots build up slow
enough that the scheduled defrag effectively eliminates the otherwise
growing problem, but it's still an additional complication to have to
configure and administer, longer term.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-09-18 2:00 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
2015-09-18 2:00 ` Duncan [this message]
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='pan$270e2$4b4f9ec6$a323af50$ada695ce@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).