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:12 +0200 [thread overview]
Message-ID: <1285759512.23010.1.camel@o> (raw)
In-Reply-To: <4CA261C5.7070005@cfl.rr.com>
On Tue, 2010-09-28 at 17:44 -0400, 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?
Like Hanness mentioned: you can free space.
>
> > +Create an ext4 filesystem on the thin provisioned device:
> > +mkfs -t ext4 /dev/mapper/thinp1
>
> FYI, that tends to spend a lot of time writing hundreds of mb of zeros
> to the inode tables, allocating chunks from the backing store. You
> might want to add -E lazy_itable_init to stop that.
Thanks for the hint, I waned to have load on the thin provisioned
devices so far for testing but will have a look at the reduced
allocations with this option.
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
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
2010-09-29 11:25 ` Heinz Mauelshagen [this message]
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=1285759512.23010.1.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 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).