From: David Teigland <teigland@redhat.com>
To: Bernd <ecki@zusammenkunft.net>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] lvm/openstack: stripe all volumes and distribute them round robin on PVs
Date: Wed, 10 May 2017 11:58:40 -0500 [thread overview]
Message-ID: <20170510165840.GB27800@redhat.com> (raw)
In-Reply-To: <CABOR3+xoAwjiE2G_OWS=z7t=GVGSR_=QtpJ8gdP+2e95-kCB1w@mail.gmail.com>
On Wed, May 10, 2017 at 01:13:37PM +0200, Bernd wrote:
> Hello,
>
> when using local lvm2 logical volumes for OpenStack Nova ephemeral pool
> then the created logical volumes are linear (not striped) and what is worse
> than that, all volumes are allocated on the same first physical volume
> (until it is filled up).
>
> I made a ServerFault question about that:
>
> https://serverfault.com/questions/849088/automatically-distribute-lvm-stripes-for-specific-lvm2-vg-on-linux/849255#849255
>
> It was suggested that raid_stripe_all_devices should help (to turn on
> striping by default), but it did not. So I went ahead and patched the
> lvm.py of nova to turn the striping on. However I still wonder if there is
> a lvm option (allocation policy for that).
>
> Besides that, it looks like it is still creating the first stripe on the
> first device. It would make more sense to have it (even in the linear case)
> to round robin the LVs. Because first of all it might be the most busy part
> of the volume and secondly it helps for keeping room for expanding volumes.
>
> Is there anything planned in this direction?
If you're concerned with placement of LVs on PVs, I'd probably skip
striping and add some logic specifying different PVs directly:
lvcreate -n name -L size VG PV ...
means the LV will be created using only the specified PVs.
next prev parent reply other threads:[~2017-05-10 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 11:13 [linux-lvm] lvm/openstack: stripe all volumes and distribute them round robin on PVs Bernd
2017-05-10 16:58 ` David Teigland [this message]
2017-05-12 9:25 ` Bernd Eckenfels
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=20170510165840.GB27800@redhat.com \
--to=teigland@redhat.com \
--cc=ecki@zusammenkunft.net \
--cc=linux-lvm@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).