From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] btrfs and sparse VM image files
Date: Sun, 18 May 2014 13:28:53 +0100 [thread overview]
Message-ID: <20140518132853.18e0a5b0@digimed.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 489 bytes --]
I'm confused about the desirability of keeping VM image files, usually
space qcow files, on a btrfs volume. I have read the advice about using
chattr +C on the subvolume, but are there any other gotchas? The btrfs
wiki says in one place that using sparse file on btrfs is not a good
idea, but is that still the case. There is conflicting information out
there, does anyone here have any hard experience?
--
Neil Bothwick
Beware of the opinion of someone without any facts.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2014-05-18 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-18 12:28 Neil Bothwick [this message]
2014-05-19 6:55 ` [gentoo-user] btrfs and sparse VM image files Stefan G. Weichinger
2014-05-19 10:07 ` Marc Stürmer
2014-05-19 11:01 ` Neil Bothwick
2014-05-19 13:03 ` Rich Freeman
2014-05-20 7:46 ` Stefan G. Weichinger
2014-05-25 8:37 ` Marc Stürmer
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=20140518132853.18e0a5b0@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.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