From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: VM nocow, should VM software set +C by default?
Date: Fri, 21 Feb 2014 17:56:45 +0000 (UTC) [thread overview]
Message-ID: <pan$d989e$d5cf11f5$8a41e137$a3391985@cox.net> (raw)
In-Reply-To: A2EE3F12-97D9-46CD-8360-ACCFF71F149B@colorremedies.com
Chris Murphy posted on Fri, 21 Feb 2014 09:55:50 -0700 as excerpted:
> Use case is a user who doesn't know that today xattr +C ought to be set
> on vm images when on Btrfs. They use e.g. Gnome Boxes, or Virtual
> Machine Manager (virt-manager) to configure pools, images, and VMs.
>
> If libvirt were to set +C on any containing directory configured as a
> pool, then any copied as well as newly created images would inherit +C.
> So is this the long term recommended practice, and should various VM
> projects be asked to build this functionality? Or will there be
> optimizations, such as autodefrag, that will obviate the need for +C on
> such VM images in the somewhat near future?
FWIW...
I had suggested/predicted in an earlier post that having the software set
NOCOW automatically for VMs, larger databases and pre-allocated files
such as those used by bittorrent clients would become long term practice,
but one of the devs (IIRC Bacik) suggested there was still ongoing defrag
work, that they hoped would ultimately eliminate the need for that.
I'm personally somewhat skeptical and expect NOCOW will always be of some
help in that regard, and still predict at least some of the apps will
begin setting it if they detect that they're on btrfs, at some point, but
I've been overrules by an expert in the domain, something I'm most
assuredly NOT, so...
I'll allow that it's a bit early to be asking for it ATM, but I also
believe it's safe to say that regardless of /future/ developments, if a VM
suite or db wishes to be ahead of the curve /today/ with its btrfs
support, they should probably at least mention it in the documentation.
As for implementing it in code, I'd say only if they're ready to take it
out later if btrfs as it matures proves not to need it, but certainly,
mentioning it in documentation, should they choose to specifically
mention btrfs at all, is probably a good idea at this point.
In my definitely NOT-a-btrfs-code-expert opinion, of course. =:^)
--
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:[~2014-02-21 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 16:55 VM nocow, should VM software set +C by default? Chris Murphy
2014-02-21 17:56 ` Duncan [this message]
2014-02-25 9:16 ` Justin Ossevoort
2014-02-25 17:44 ` Chris Murphy
2014-02-25 17:53 ` Jim Salter
2014-02-25 18:33 ` Chris Murphy
2014-02-26 5:43 ` Duncan
2014-02-25 18:01 ` Roman Mamedov
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$d989e$d5cf11f5$8a41e137$a3391985@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).