From: Sebastian Riemer <sebastian.riemer@profitbricks.com>
To: James Hawtin <oolon@ankh.org>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Allocation Policy for Cloud Computing needed
Date: Thu, 16 Feb 2012 16:27:15 +0100 [thread overview]
Message-ID: <4F3D2053.7070401@profitbricks.com> (raw)
In-Reply-To: <4F3D1593.9070609@ankh.org>
Hi James,
thank you for your idea, but this is exactly what I don't want. I want
to have the LV completely on one PD if possible (but not all on the
first). Only if the customer requests more than the capacity of a single
hard drive I would provide striping, but only on that volume.
If all customers can access all hard drives at the same time this
results into very slow random IO. I've seen that on SW RAID-10. All the
rw-heads need to be repositioned over and over again.
Cheers,
Sebastian
On 16/02/12 15:41, James Hawtin wrote:
> I wrote a script to do this, with LVM 1 that just extended the lv in
> chunks over a range of PVs until it was full. while it worked on LVM
> it produced lots of backups in /etc. I felt with the LVM stripe
> function that this was not necessary, and could acheive the same
> thing by using large stripe size, as LVM allows concats of different
> stripeness it was not a problem extending the lv.
next prev parent reply other threads:[~2012-02-16 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 13:50 [linux-lvm] Allocation Policy for Cloud Computing needed Sebastian Riemer
2012-02-16 14:41 ` James Hawtin
2012-02-16 15:27 ` Sebastian Riemer [this message]
2012-02-20 21:59 ` Lars Ellenberg
2012-02-20 22:41 ` Ray Morris
2012-02-21 9:48 ` Sebastian Riemer
2012-02-21 9:34 ` Sebastian Riemer
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=4F3D2053.7070401@profitbricks.com \
--to=sebastian.riemer@profitbricks.com \
--cc=linux-lvm@redhat.com \
--cc=oolon@ankh.org \
/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.