![[ Register ]](/images/navbar/register.gif)
![[ Applications ]](/images/navbar/applications.gif)
![[ Documentation ]](/images/navbar/documentation.gif)
![[ Distributions ]](/images/navbar/distributions.gif)
![[ Download Info ]](/images/navbar/download.gif)
![[ General Info ]](/images/navbar/geninfo.gif)
![[ Book Store ]](/images/navbar/bookstore.gif)

![[ Courses ]](/images/navbar/courses.gif)
![[ News ]](/images/navbar/news.gif)
![[ People ]](/images/navbar/people.gif)
![[ Hardware ]](/images/navbar/hardware.gif)
![[ Vendors ]](/images/navbar/vendors.gif)
![[ Projects ]](/images/navbar/projects.gif)
![[ Events ]](/images/navbar/events.gif)
![[ User Groups ]](/images/navbar/usergroups.gif)
![[ User Area ]](/images/navbar/user_area.gif)

![[ About Us ]](/images/navbar/aboutus.gif)
![[ Home Page ]](/images/navbar/homepage.gif)
![[ Advertise ]](/images/navbar/advertise.gif) |

| mapping modes (linear/striped) |
|---|
3.7. mapping modes (linear/striped)
The administrator can choose between a couple of general strategies
for mapping logical extents onto physical extents:
Linear mapping will assign a
range of PE's to an area of an LV in order eg., LE 1 - 99 map to
PV1 and LE 100 - 347 map onto PV2.
Striped mapping will interleave
the chunks of the logical extents across a number of physical
volumes eg.,
1st chunk of LE[1] -> PV1[1],
2nd chunk of LE[1] -> PV2[1],
3rd chunk of LE[1] -> PV3[1],
4th chunk of LE[1] -> PV1[2],
|
and so on. In certain situations this strategy can
improve the performance of the logical volume.
 | LVM 1 Caveat |
|---|
| |
LVs created using striping cannot be extended past
the PVs they were originally created on in LVM 1.
|
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?
|
 |
|