From: AJ Lewis <alewis@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Extending a LVM2 strip set
Date: 23 Sep 2004 13:45:52 -0500 [thread overview]
Message-ID: <x05k6ukomcf.fsf@null.msp.redhat.com> (raw)
In-Reply-To: <mailman.2865.1095960324.3231.linux-lvm@redhat.com>
lemons_terry@emc.com writes:
> http://www.tldp.org/HOWTO/LVM-HOWTO/mapmode.html
> <http://www.tldp.org/HOWTO/LVM-HOWTO/mapmode.html> states:
>
> "In LVM 2, striped LVs can be extended by concatenating another set of
> devices onto the end of the first set. So you can get into a situation where
> your LV is a 2 stripe set concatenated with a linear set concatenated with a
> 4 stripe set. Are you confused yet?"
>
> As a matter of fact, I am!
>
> I need to start with a 2 disk (therefore, 2 stripe) logical volume, that I
> later extend with 2 more disks. How is this done?
In lvm2 you simply create the lv with a stripe size of 2, then later
when you want to extend it, you lvextend it with a stripe size of 2.
The reason this is explained in so much detail is that in LVM1, you
could not extend a striped set past its original PVs. In LVM2, the
original striped set can be extended to the end of the original PVs,
and any additional PVs become a striped set that is tacked on to the
end (concatenated).
Maybe an ACSII picture can help ;)
Original striped volumes:
___ ___
| 1 | | 2 |
| 3 | | 4 |
|_5_| |_6_|
After adding two more disks and lvextending:
___ ___ ___ ___
| 1 | | 2 | | 7 | | 8 |
| 3 | | 4 | | 9 | | 10|
|_5_| |_6_| |_11| |_12|
So you have 2 sets of striped segments (with 2 stripes each),
concatenated together. It does *not* remap all the striping so you
have 1 set of striped segments (with 4 stripes each).
Is that any clearer?
--
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...
next parent reply other threads:[~2004-09-23 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2865.1095960324.3231.linux-lvm@redhat.com>
2004-09-23 18:45 ` AJ Lewis [this message]
2004-09-24 17:10 [linux-lvm] Extending a LVM2 strip set lemons_terry
-- strict thread matches above, loose matches on Subject: below --
2004-09-24 4:23 lemons_terry
2004-09-23 17:25 lemons_terry
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=x05k6ukomcf.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 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.