From: Joe Thornber <thornber@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: dm-thin - issue about the maximum size of the metadata device
Date: Tue, 9 Sep 2014 16:54:55 +0100 [thread overview]
Message-ID: <20140909155454.GD2967@debian> (raw)
In-Reply-To: <20140909155240.GC2967@debian>
Sorry for raising this thread from the dead. My mail was sorted by
sender rather than received time. Please ignore.
On Tue, Sep 09, 2014 at 04:52:40PM +0100, Joe Thornber wrote:
> On Tue, Aug 06, 2013 at 12:18:22PM +0800, 梁文彥 wrote:
> > In this experiment, we run out of the metadata, and by the "Allocated pool
> > data" field, we infered that the maximum thin device was about 30.59TB, was
> > it correct?
>
> Sounds about right. Use a bigger block size if you want to provision
> more space in the pool.
>
> - Joe
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
prev parent reply other threads:[~2014-09-09 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 4:18 dm-thin - issue about the maximum size of the metadata device 梁文彥
2013-08-06 10:39 ` Zdenek Kabelac
2014-09-09 15:52 ` Joe Thornber
2014-09-09 15:54 ` Joe Thornber [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=20140909155454.GD2967@debian \
--to=thornber@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).