linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Stuart D. Gathman" <stuart@bmsi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM questions
Date: Thu, 29 Mar 2007 13:38:50 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0703291325420.29826-100000@bmsred.bmsi.com> (raw)
In-Reply-To: <460BEF90.60900@ehsco.com>

On Thu, 29 Mar 2007, Eric A. Hall wrote:

> I have seen some people talk about creating hundreds of small partitions
> and using those for moving and resizing. Is this needed, desirable, or
> just a stupid human trick?

That is a work around for lack of functionality in LVM.  Having used
LVM on AIX, that is the gold standard for me.  The LVM divides into
little partitions and keeps track of them for you.  So why do it 
manually?  Using md for mirroring, each partition synchronizes separately.
Manually making several smaller partitions lets you move them around and resync
- all while the system is running.  This happens automatically when LVM
supports mirroring, but LVM mirroring is still a new experimental feature
on linux.

Multiple volume groups just get in the way when you are resizing and
migrating between physical volumes.  You need a separate volume group
when you need to physically pick up the entire volume group and 
take it somewhere else.  For instance, scientific datasets are
often much too large (terabytes) for DVD, tape, or internet.  So, just make a
volume group on a handful of 500G drives, build and process your data
there, then deactivate the VG and send the drives to your colleague
(make a copy first, of course).  Your colleague plugs the drives into
his USB/SATA/iSCSI/whatever controller, activates the volume group,
and now has a copy of your work.

For anything that will never be physically moved to another machine, keep
it all on one volume group.  But, for instance, if you think you might
want to move the iSCSI data to another box at some point, keep it 
in its own VG (with its own set of drives) to make that easy.

-- 
	      Stuart D. Gathman <stuart@bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.

  reply	other threads:[~2007-03-29 17:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-29 16:55 [linux-lvm] LVM questions Eric A. Hall
2007-03-29 17:38 ` Stuart D. Gathman [this message]
2007-04-20 13:36   ` Nix
  -- strict thread matches above, loose matches on Subject: below --
2008-03-27 22:27 [linux-lvm] LVM Questions Nicholas Muguira
2008-04-02  8:20 ` Jordi Prats
2001-05-03  0:48 Darren Young
2001-05-03  1:26 ` Glenn Shannon
2001-05-03  1:45 ` Evan Day
2001-05-03  6:56   ` Adrian Phillips
2001-05-04  9:33     ` Heinz J. Mauelshagen
2001-05-04  7:45       ` Adrian Phillips
2001-05-04 10:38         ` Heinz J. Mauelshagen
2001-05-04  9:38           ` Adrian Phillips
2001-05-04 13:39             ` Heinz J. Mauelshagen
2001-05-03 11:15   ` Heinz J. Mauelshagen
2001-05-03 11:41 ` Carlo Marcelo Arenas Belon
2001-05-04  1:59   ` Mark van Walraven

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=Pine.LNX.4.44.0703291325420.29826-100000@bmsred.bmsi.com \
    --to=stuart@bmsi.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).