From: Heinz Mauelshagen <heinzm@redhat.com>
To: dm-devel@redhat.com
Subject: Re: About the thin provision function @ kernel 3.2 or later.
Date: Mon, 16 Jan 2012 17:21:06 +0100 [thread overview]
Message-ID: <4F144E72.9030604@redhat.com> (raw)
In-Reply-To: <CACaC9DzwWWdy3YBrs1KMx6RnwvU8wC2q_OrVTCzp2+rbEirBVQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2794 bytes --]
On 01/16/2012 02:27 AM, Yukihito HARA wrote:
> Hi, I'm Yukihito, and interested in Linux system.
Hi.
>
> Recently days, I became happy to hear that Linux kernel start to
> support thin-provisioning function.
> And not trying to how it work on latest kernel.
>
> According to the word "thin provisioning", I'm imaging that, I can get
> larger space than actual disk size. This image is born from
> thin-provisioning system working on VMWare series.
Thin provisioning iis a general design to save storage costs.
There's solutions in software and hardware in the market, including VMWare.
Higher range storage systems feature it.
> And can write the files until reach to the physical maximum. Once
> reach to the physical maximum, I can't write any more files to that
> volume, but I can write more files after add additional physical disks
> to thin-pool.
Yes.
>
> I could create the pool according to the documents included in the
> kernel source(Documentation/device-mapper/thin-provisioning.txt).
> But I'm not sure, it works as I expecting like above.
>
> So can you provide more detailed documentation about the
> thin-provisioning, if you have?
Did you read Documentation/device-mapper/thin-provisioning.txt in the
kernel source tree to use it yet?
It provides advice how to create thin-provisioned devices and snapshots
(see dmsetup message examples).
> There're no documentation written in Japanese, so I'll also output
> this communication to wiki or my twitter in Japanese. It helpful to
> make your work more major among Japanese IT engineers. And you can get
> more feedback if the challengers in Japan will be increased.
> The worst point of the current documentation is, it's not instruct
> about how to use like above. Can't get image how to use this like
> VMware system from that document.
Keep in mind that there'll be LVM2 support available later in distributions.
You can pull that code from the HEAD of the LVM2 upstream repository for
testing purposes already (not meant for production use obviously).
>
> Sorry, this is my private testing, not for work. So I can't get much
> time to this, but very interested in.
Thanks for trying it, we're interested in external feedback.
Regards,
Heinz
>
>
> I'm looking forward to your answer.
>
> Thank you.
> Yukihito.
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
--
===============================================================
Heinz Mauelshagen +49 2626 141200
Consulting Development Engineer FAX +49 2626 924446
Red Hat GmbH
Am Sonnenhang 11
56242 Marienrachdorf
Germany heinzm@redhat.com
===============================================================
[-- Attachment #1.2: Type: text/html, Size: 4709 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2012-01-16 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 1:27 About the thin provision function @ kernel 3.2 or later Yukihito HARA
2012-01-16 14:14 ` Mike Snitzer
2012-01-16 14:38 ` Joe Thornber
2012-01-16 15:59 ` Ted Ts'o
2012-01-17 10:13 ` Joe Thornber
2012-01-17 15:59 ` Ted Ts'o
2012-01-19 9:14 ` Joe Thornber
2012-01-27 16:04 ` Joe Thornber
2012-01-16 16:21 ` Heinz Mauelshagen [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=4F144E72.9030604@redhat.com \
--to=heinzm@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).