linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Abraham Pérez" <jockah@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Best Practices deploying LVM
Date: Fri, 30 Oct 2009 09:52:43 +0100	[thread overview]
Message-ID: <868096450910300152s271d34dcl74980fff211d15b4@mail.gmail.com> (raw)
In-Reply-To: <20091030004218.GA11054@us.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 2440 bytes --]

Thanks for the instant answers!

Well... I'll try to explain myself better. I'm working in a client who have
a lot of servers running under VMware. This client have a lot of problems
with the storage, because they never have enough space so when they have to
allocate disk in servers, they add small virtual hard disks with, for
example, 5 or 10GB.

Then for the OS installation, we follow the basic schema based on disk
partitions (/dev/sda1 pointing to / with ext3, /dev/sda2 pointing to /home
and so on) and for the applications data, we use VG and LV pointing to /opt

The client have some applications who need a lot of mountpoints, so my
colleague adds 1-3 LV per VG (aproximated) and I only create only one VG and
inside it, different LVs.  With this infrastructure, we have to discard
different kinds of hard disk because they're exactly the same... and we have
that doubt: what schema is better and why, discarding concept things like a
volume group was designed to be a group, because we're looking for good
reasons based in performance of future actions, it's not important... or am
I mistaken???

I don't know if I explained myself very well, so thanks all anyway!

Regards,
Abraham Pérez

2009/10/30 <malahal@us.ibm.com>

> Ray Morris [support@bettercgi.com] wrote:
> >     I don't know about a whitepaper, but I can address
> > your example.
> >
> > > he makes one volume group for each logical volume (more or less)
> >
> >     If each one has one volume, that's not exactly a volume
> > GROUP, is it?  If groups and volumes are basically synomous,
> > he gives up all the benfits of groups.  In fact, he gives
> > up most of the benefits of logical volumes, since each PV
> > has to be in one group, and each VG is one LV, you're left
> > with one LV per PV - might as well just use partitions
> > directly.
>
> I agree, you lose some flexibility but it has some advantage compared to
> plain partitions without LVM. E.g. he can make a file system larger than
> any disk with multiple disks in the above LVM (one LV per VG)
> configuration.  There are other advantages. I am not sure the reason for
> making only one LV per VG though!
>
> Thanks, Malahal.
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>

[-- Attachment #2: Type: text/html, Size: 3135 bytes --]

  reply	other threads:[~2009-10-30  8:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29 23:45 [linux-lvm] Best Practices deploying LVM Abraham Pérez
2009-10-29 23:58 ` Chris Cox
2009-10-30  0:00 ` Ray Morris
2009-10-30  0:42   ` malahal
2009-10-30  8:52     ` Abraham Pérez [this message]
2009-10-30 19:46       ` Ray Morris
2009-10-30 21:03         ` Abraham Pérez

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=868096450910300152s271d34dcl74980fff211d15b4@mail.gmail.com \
    --to=jockah@gmail.com \
    --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).