All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Austermuehle <au@hcsd.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] One VG or many?
Date: Wed Jun  5 03:09:01 2002	[thread overview]
Message-ID: <20020605100920.R8663@babbage.hcsd.de> (raw)
In-Reply-To: <F888C30C3021D411B9DA00B0D0209BE8038F951A@cvo-exchange.cvo.roguewave.com>; from petersp@roguewave.com on Tue, Jun 04, 2002 at 02:03:38PM -0700

On Tue, Jun 04, 2002 at 02:03:38PM -0700, Poul Petersen wrote:

> We have about 2TB to slice up and using a single VG seems to provide
> the most flexibility for usage of the space. However, using one VG

First, I would separate system (= containing the OS) and data area.
Second, if you do not intend to stripe data across LVs I would create
one VG for every logical business/application unit and assign disk
space on demand. That means that you leave most disks in a pool and
if you need more space in one VG you'll add the disk online with
vgextend. Why not start with one disks per VG?

If you plan to use the striping feature of LVM you should think of
what is sane looking at the two aspects speed and cost of extension
(e.g., striping across four disks requires you to add four disks at a
time if you need more space).

Stephan

  reply	other threads:[~2002-06-05  3:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-04 16:07 [linux-lvm] One VG or many? Poul Petersen
2002-06-05  3:09 ` Stephan Austermuehle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-05 14:37 Poul Petersen
2002-06-05 16:14 ` Goetz Bock
2002-06-05 16:18   ` Goetz Bock
2002-06-06  2:52 ` Stephan Austermuehle

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=20020605100920.R8663@babbage.hcsd.de \
    --to=au@hcsd.de \
    --cc=linux-lvm@sistina.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.