From: Xavier Gnata <xavier.gnata@gmail.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: btrfs autodefrag?
Date: Sat, 17 Oct 2015 18:36:32 +0200 [thread overview]
Message-ID: <56227910.7000208@gmail.com> (raw)
Hi,
On a desktop equipped with an ssd with one 100GB virtual image used
frequently, what do you recommend?
1) nothing special, it is all fine as long as you have a recent kernel
(which I do)
2) Disabling copy-on-write for just the VM image directory.
3) autodefrag as a mount option.
4) something else.
I don't think this usecase is well documented therefore I asked this
question.
Xavier
next reply other threads:[~2015-10-17 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-17 16:36 Xavier Gnata [this message]
2015-10-18 5:46 ` btrfs autodefrag? Duncan
2015-10-18 12:44 ` Xavier Gnata
2015-10-19 6:04 ` Paul Harvey
2015-10-18 14:24 ` Rich Freeman
2015-10-18 14:40 ` Hugo Mills
2015-10-19 6:19 ` Erkki Seppala
2015-10-19 11:56 ` Austin S Hemmelgarn
2015-10-19 16:13 ` Erkki Seppala
2015-10-19 19:48 ` 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=56227910.7000208@gmail.com \
--to=xavier.gnata@gmail.com \
--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