From: thornber@redhat.com
To: LVM2 development <lvm-devel@redhat.com>
Cc: dm-devel@redhat.com
Subject: Re: Default low water mark threshold for a new thin pool
Date: Tue, 5 Feb 2013 12:18:47 +0000 [thread overview]
Message-ID: <20130205121846.GB3082@raspberrypi> (raw)
In-Reply-To: <87ehgv16gf.fsf@in.ibm.com>
On Tue, Feb 05, 2013 at 02:30:00PM +0530, M. Mohan Kumar wrote:
>
> Hello,
>
> We are adding a lvm2api for creating a thin pool. During thin pool
> creation if user does not specify anything for the low water mark
> thresold, it would result in 0 and no events will be generated when thin
> pool capacity is reaching its full size.
An event will be generated.
> I am not sure what should be the default low water threshold
> percentage. Is there any recommended value for low water threshold value
> in dm thin pools?
It's very hard to say since it depends on your use case. In general
you want to allow dmeventd plenty of time to extend the pool before
you run out of space. So if you're seeing a _peak_ provisioning rate of
100meg a minute, I'd set the lwm to about 100meg. It would be nice if LVM
could help you through this process.
- Joe
--
lvm-devel mailing list
lvm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/lvm-devel
WARNING: multiple messages have this Message-ID (diff)
From: thornber@redhat.com <thornber@redhat.com>
To: lvm-devel@redhat.com
Subject: Default low water mark threshold for a new thin pool
Date: Tue, 5 Feb 2013 12:18:47 +0000 [thread overview]
Message-ID: <20130205121846.GB3082@raspberrypi> (raw)
In-Reply-To: <87ehgv16gf.fsf@in.ibm.com>
On Tue, Feb 05, 2013 at 02:30:00PM +0530, M. Mohan Kumar wrote:
>
> Hello,
>
> We are adding a lvm2api for creating a thin pool. During thin pool
> creation if user does not specify anything for the low water mark
> thresold, it would result in 0 and no events will be generated when thin
> pool capacity is reaching its full size.
An event will be generated.
> I am not sure what should be the default low water threshold
> percentage. Is there any recommended value for low water threshold value
> in dm thin pools?
It's very hard to say since it depends on your use case. In general
you want to allow dmeventd plenty of time to extend the pool before
you run out of space. So if you're seeing a _peak_ provisioning rate of
100meg a minute, I'd set the lwm to about 100meg. It would be nice if LVM
could help you through this process.
- Joe
next prev parent reply other threads:[~2013-02-05 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-05 9:00 Default low water mark threshold for a new thin pool M. Mohan Kumar
2013-02-05 9:00 ` M. Mohan Kumar
2013-02-05 12:18 ` thornber [this message]
2013-02-05 12:18 ` thornber
2013-02-05 16:56 ` M. Mohan Kumar
2013-02-05 16:56 ` M. Mohan Kumar
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=20130205121846.GB3082@raspberrypi \
--to=thornber@redhat.com \
--cc=dm-devel@redhat.com \
--cc=lvm-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.