From: Heinz Mauelshagen <heinzm@redhat.com>
To: 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 13:25:36 +0200 [thread overview]
Message-ID: <1285759536.23010.2.camel@o> (raw)
In-Reply-To: <4CA2DCCE.3070905@suse.de>
On Wed, 2010-09-29 at 08:29 +0200, Hannes Reinecke wrote:
> Phillip Susi wrote:
> > On 9/28/2010 4:49 PM, Heinz Mauelshagen wrote:
> >> These are 2 new device mapper targets "thinp" and "thinp-dev"
> >> implemented in one module, which allow for thin provisioning of storage
> >> on a single host from a storage pool to an arbitrary amount of devices.
> >
> > How is this different than snapshotting a zero target?
> >
> Main difference is that you actually can free up space.
> You can't with snapshotting as then a rollback
> becomes impossible.
>
Yes, that's right.
Heinz
> Cheers,
>
> Hannes
next prev parent reply other threads:[~2010-09-29 11:25 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 [this message]
2010-09-29 11:25 ` Heinz Mauelshagen
2010-09-29 13:41 ` Phillip Susi
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=1285759536.23010.2.camel@o \
--to=heinzm@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@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 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.