Linux LVM users
 help / color / mirror / Atom feed
From: AJ Lewis <alewis@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] How can I restripe LVs on addition of extra PVs?
Date: 14 Oct 2004 08:52:36 -0500	[thread overview]
Message-ID: <x053c0h4daz.fsf@null.msp.redhat.com> (raw)
In-Reply-To: <mailman.10762.1097732995.3231.linux-lvm@redhat.com>

Clint Byrum <cbyrum@spamaps.org> writes:

> On Wednesday, October 13, 2004, at 06:12 PM, Daniel . wrote:
> 
> > Hi,
> >
> > [I'm only familiar with LVM1, so that's what I'm referring to in the
> > rest of the mail.  I probably could move to LVM2 if it solves my
> > problems.]
> >
> > I'm planning on using LVM to create LVs striped across multiple PVs
> > (which, incidentally, are RAID 1 mirrorred partitions).
> > In the future I will need to add extra PVs to the VG and extend the
> > LVs.
> >
> 
> This just came up in #lvm on freenode today. I don't think this is at
> all possible with LVM1. Once the striping is done for an LV, that LV
> cannot be extended past the physical extents that were allocated at
> that time.
> 
> However, with LVM2, you could write a script to do this by manually
> running pvmove over and over, doing something like "pvmove dev:1-8
> otherdev;pvmove otherdev:1-8 dev;" .. It gets rather complex to figure
> this out on the cmdline, but I do believe it can be done and you would
> end up with PE's evenly spread out over all PVs.
> 
> Somebody tell me this is wrong and stupid before I try it. ;)

One problem I see with doing this is that your LVM metadata is going
to get rather large after you've done this.  Because you're mucking
with the segments through pvmove, lvm doesn't know that you're trying
to convert a stripe set of 2 to a stripe set of 4 or whatever.  I'm
not positive, but it seems like this could be a problem.

Also, remember that stripe size is different then segment size, and
segment size is the level at which pvmove manipulates things.  So
that's probably not going to do what you want it to.

Regards,
-- 
AJ Lewis                                   Voice:  612-638-0500
Red Hat Inc.                               E-Mail: alewis@redhat.com
720 Washington Ave. SE, Suite 200
Minneapolis, MN 55414
   
Current GPG fingerprint = D9F8 EDCE 4242 855F A03D  9B63 F50C 54A8 578C 8715
Grab the key at: http://people.redhat.com/alewis/gpg.html or one of the
many keyservers out there...

       reply	other threads:[~2004-10-14 13:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.10762.1097732995.3231.linux-lvm@redhat.com>
2004-10-14 13:52 ` AJ Lewis [this message]
2004-10-14 22:58 [linux-lvm] How can I restripe LVs on addition of extra PVs? Daniel .
  -- strict thread matches above, loose matches on Subject: below --
2004-10-14 20:10 Daniel .
2004-10-14  1:12 Daniel .
2004-10-14  5:49 ` Clint Byrum
2004-10-14 21:27 ` Markus Baertschi

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=x053c0h4daz.fsf@null.msp.redhat.com \
    --to=alewis@redhat.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