From: Phillip Susi <psusi@cfl.rr.com>
To: heinzm@redhat.com, device-mapper development <dm-devel@redhat.com>
Cc: agk@redhat.com
Subject: Re: [PATCH] dm-thinp: new device mapper target to thin provision storage
Date: Wed, 29 Sep 2010 09:41:05 -0400 [thread overview]
Message-ID: <4CA341F1.70305@cfl.rr.com> (raw)
In-Reply-To: <1285759512.23010.1.camel@o>
On 9/29/2010 7:25 AM, Heinz Mauelshagen wrote:
> On Tue, 2010-09-28 at 17:44 -0400, Phillip Susi wrote:
>> How is this different than snapshotting a zero target?
>
> Like Hanness mentioned: you can free space.
Could you clarify that a bit? Is space only freed if you reduce the
length of a device? You can't do the same with a snapshot?
next prev parent reply other threads:[~2010-09-29 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 20:49 [PATCH] dm-thinp: new device mapper target to thin provision storage Heinz Mauelshagen
2010-09-28 21:44 ` Phillip Susi
2010-09-29 6:29 ` Hannes Reinecke
2010-09-29 11:25 ` Heinz Mauelshagen
2010-09-29 11:25 ` Heinz Mauelshagen
2010-09-29 13:41 ` Phillip Susi [this message]
2010-09-29 15:20 ` Heinz Mauelshagen
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=4CA341F1.70305@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=heinzm@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).