From: Roman Mamedov <rm@romanrm.net>
To: "Devon B." <devon.b@virtualcomplete.com>, linux-btrfs@vger.kernel.org
Subject: Re: Accepting discard to free space from disk images
Date: Mon, 9 Feb 2015 11:40:23 +0500 [thread overview]
Message-ID: <20150209114023.137402bf@natsu> (raw)
In-Reply-To: <54D842FD.1010806@virtualcomplete.com>
On Mon, 09 Feb 2015 00:17:49 -0500
"Devon B." <devon.b@virtualcomplete.com> wrote:
> Looking to use btrfs with disk images that contain ext4, xfs, and other
> possible filesystems. One of my main concerns is reclaiming disk space
> when files are deleted on the disk image's filesystem. Using fstrim on
> the mount point of the disk image or mounting the disk image (loop) with
> discard doesn't appear to pass the freed blocks to btrfs.
>
> The image file on the btrfs filesystem just keeps growing in size. When
> hosting images on ext4, using fstrim or discard frees up the space on
> the host filesystem (ext4).
>
> I see discard is pretty well supported for btrfs to the underlying block
> devices but is there any way to properly free space on the btrfs host
> filesystem from overlying filesystems while they are online?
I use KVM (QEMU) with discard pass-through from the VM guest ("discard=unmap"
option), with the VM images stored on Btrfs. It works just fine, the disk
space used for the image file does shrink when the guest OS issues discards on
its FS. Maybe there is a difference in how KVM and the 'loop' module submit
discards to Btrfs?
--
With respect,
Roman
next prev parent reply other threads:[~2015-02-09 6:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 5:17 Accepting discard to free space from disk images Devon B.
2015-02-09 6:40 ` Roman Mamedov [this message]
2015-02-09 8:39 ` Hugo Mills
2015-02-09 9:12 ` Roman Mamedov
2015-02-09 9:15 ` Hugo Mills
[not found] ` <54D8D1A9.1070006@virtualcomplete.com>
2015-02-09 15:42 ` Roman Mamedov
2015-02-09 15:45 ` Roman Mamedov
[not found] ` <54D8E946.8060900@virtualcomplete.com>
2015-02-09 17:27 ` Roman Mamedov
2015-02-09 18:08 ` Devon B.
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=20150209114023.137402bf@natsu \
--to=rm@romanrm.net \
--cc=devon.b@virtualcomplete.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.