Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Hugo Mills <hugo@carfax.org.uk>
Cc: "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 14:12:21 +0500	[thread overview]
Message-ID: <20150209141221.099d4fe5@natsu> (raw)
In-Reply-To: <20150209083941.GI28427@carfax.org.uk>

[-- Attachment #1: Type: text/plain, Size: 812 bytes --]

On Mon, 9 Feb 2015 08:39:41 +0000
Hugo Mills <hugo@carfax.org.uk> wrote:

> > 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?
> 
>    This is interesting, because I've tried exactly that setup (KVM,
> discard=unmap) and it's not worked for me.

Did you use the emulated IDE interface in KVM? Others such as virtio, ahci and
maybe SCSI may not support discard. Did you get a successful result issuing
TRIM within the guest (e.g. fstrim -v / succeeds and doesn't -ENOSUPP)?


-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-02-09  9:12 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
2015-02-09  8:39   ` Hugo Mills
2015-02-09  9:12     ` Roman Mamedov [this message]
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=20150209141221.099d4fe5@natsu \
    --to=rm@romanrm.net \
    --cc=devon.b@virtualcomplete.com \
    --cc=hugo@carfax.org.uk \
    --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