linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Paul B. Henson" <henson@acm.org>
To: 'Marian Csontos' <mcsontos@redhat.com>,
	'LVM general discussion and development' <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] migrating a thick LV to a thin LV
Date: Wed, 12 Mar 2014 12:07:37 -0700	[thread overview]
Message-ID: <0bf101cf3e26$57024680$0506d380$@acm.org> (raw)
In-Reply-To: <53201EF8.3020104@redhat.com>

> From: Marian Csontos
> Sent: Wednesday, March 12, 2014 1:47 AM
>
> Yes, discarded blocks in the thin-pool data device which are not
> referenced from other thin-volumes (snapshots) are released regardless
> whether the device at the bottom supports discards or not.

Excellent; thanks for the confirmation.

      reply	other threads:[~2014-03-12 19:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12  0:01 [linux-lvm] migrating a thick LV to a thin LV Paul B. Henson
2014-03-12  8:46 ` Marian Csontos
2014-03-12 19:07   ` Paul B. Henson [this message]

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='0bf101cf3e26$57024680$0506d380$@acm.org' \
    --to=henson@acm.org \
    --cc=linux-lvm@redhat.com \
    --cc=mcsontos@redhat.com \
    /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).