AN121 G 08

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
5.2
Copyright IBM Corporation 2009
Unit 8
Working with the
Logical Volume Manager
IBM Power Systems
Unit objectives
After completing this unit, you should be able to:
Explain how to work with the Logical Volume Manager
Add, change, and delete:
Volume groups
Logical volumes
Physical volumes
Describe essential LVM concepts, such as:
Mirroring
Striping

IBM Power Systems
# smit lvm


Move cursor to desired item and press Enter.

Volume Groups
Logical Volumes
Physical Volumes
Paging Space

IBM Power Systems
SMIT volume group menu
Volume Groups


List All Volume Groups
Add a Volume Group
Set Characteristics of a Volume Group
List Contents of a Volume Group
Remove a Volume Group
Activate a Volume Group
Deactivate a Volume Group
Import a Volume Group
Export a Volume Group
Mirror a Volume Group
Unmirror a Volume Group
Synchronize LVM Mirrors
Back Up a Volume Group
Remake a Volume Group
Preview Information about a Backup
Verify the Readability of a Backup (Tape only)
View the Backup Log
List Files in a Volume Group Backup
Restore Files in a Volume Group Backup
IBM Power Systems
Adding a volume group to the system
# smit mkvg

Add a Volume Group


Add an Original Volume Group
Add a Big Volume Group
Add a Scalable Volume Group
Add an Original Volume Group

[Entry Fields]
VOLUME GROUP name [datavg]
Physical partition SIZE in megabytes +
* PHYSICAL VOLUME names [hdisk1 hdisk2] +
Force the creation of a volume group? no +
Activate volume group AUTOMATICALLY yes +
at system restart?
Volume Group MAJOR NUMBER [] +#
Create VG Concurrent Capable? no +
mkvg y datavg hdisk1 hdisk2
IBM Power Systems
Adding a scalable volume group to the system
# smit mkvg

Add a Scalable Volume Group

Type or select values in entry fields.
Press Enter AFTER making all desired changes.

[Entry Fields]
VOLUME GROUP name [db2_vg]
Physical partition SIZE in megabytes +
* PHYSICAL VOLUME names [hdisk3] +
Force the creation of a volume group? no +
Activate volume group AUTOMATICALLY yes +
at system restart?
Create VG Concurrent Capable? no +
Max PPs per VG in units of 1024 32 +
Max Logical Volumes 256 +

mkvg S y db2_vg hdisk3
IBM Power Systems
Listing volume groups and VG attributes
# lsvg
rootvg
datavg
db2_vg

# lsvg -o
datavg
rootvg

# lsvg rootvg

VOLUME GROUP: rootvg VG IDENTIFIER:
00cf2e7f00004c000000011cec07b52e
VG STATE: active PP SIZE: 64 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 130 (8320 megabytes)
MAX LVs: 256 FREE PPs: 54 (3456 megabytes)
LVs: 11 USED PPs: 76 (4864 megabytes)
OPEN LVs: 9 QUORUM: 2 (Enabled)
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 2 AUTO ON: yes
MAX PPs per VG: 32512
MAX PPs per PV: 1016 MAX PVs: 32
LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable
IBM Power Systems
Listing PVs in a VG and VG contents
# lsvg -p rootvg
rootvg:
PV_NAME PV STATE TOTAL PPs FREE PPs FREE DISTRIBUTION
hdisk0 active 99 23 15..00..00..00..08
hdisk5 active 31 31 07..06..06..06..06

# lsvg -l rootvg
rootvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
hd5 boot 1 1 1 closed/syncd N/A
hd6 paging 8 8 1 open/syncd N/A
hd8 jfslog 1 1 1 open/syncd N/A
hd4 jfs 15 15 1 open/syncd /
hd2 jfs 35 35 1 open/syncd /usr
hd9var jfs 5 5 1 open/syncd /var
hd3 jfs 3 3 1 open/syncd /tmp
hd1 jfs 1 2 1 open/syncd /home
hd10opt jfs 4 4 1 open/syncd /opt
IBM Power Systems
Change a volume group
# smit chvg

Change a Volume Group

[Entry Fields]
* VOLUME GROUP name datavg
* Activate volume group AUTOMATICALLY no +
at system restart?
* A QUORUM of disks required to keep the volume no +
group on-line ?
Convert this VG to Concurrent Capable? no +
Change to big VG format? no +
Change to scalable VG format? no +
LTG Size in kbytes 256 +
Set hotspare characteristics n +
Set synchronization characteristics of stale n +
partitions
Max PPs per VG in units of 1024 32 +
Max Logical Volumes 256 +
chvg a n Q n datavg
IBM Power Systems
Extend and reduce a VG
hdisk0 hdisk1
hdisk2
# extendvg -f rootvg hdisk2
# lsvg -p rootvg | awk {print $1, $2}
rootvg:
PV_NAME PV STATE
hdisk0 active
hdisk1 active
hdisk2 active

# reducevg -f rootvg hdisk1
# lsvg -p rootvg | awk {print $1, $2}
rootvg:
PV_NAME PV STATE
hdisk0 active
hdisk2 active

hdisk1
IBM Power Systems
Remove a volume group
Remove a Volume Group

Type or select a value for the entry field.

[Entry Fields]
* VOLUME GROUP name [db2_vg] +

# smit reducevg2

reducevg -df db2_vg hdisk2 hdisk3
Note: There is no option to input disks. In this example db2_vg was contained
on hdisk3.
IBM Power Systems
Activate and deactivate a volume group
Activate a Volume Group

[Entry Fields]
* VOLUME GROUP name [datavg] +
RESYNCHRONIZE stale physical partitions? yes +
Activate volume group in SYSTEM no +
MANAGEMENT mode?
FORCE activation of the volume group? no +
Warning--this may cause loss of data integrity.
Varyon VG in Concurrent Mode? no +
Synchronize Logical Volumes? no +

# smit varyonvg

varyonvg datavg
Deactivate a Volume Group

[Entry Fields]
Put volume group in SYSTEM no +
MANAGEMENT mode?

# smit varyoffvg

varyoffvg datavg
IBM Power Systems
Import and export a volume group
Import a Volume Group

[Entry Fields]
VOLUME GROUP name [datavg]
* PHYSICAL VOLUME name [hdisk3] +

# smit importvg

importvg y datavg hdisk3
Export a Volume Group

[Entry Fields]

# smit exportvg

exportvg datavg
Note: Volume group must be inactive before it is exported.
IBM Power Systems
Reorganize a Volume Group
# smit reorgvg

Reorganize a Volume Group

[Entry Fields]
* VOLUME GROUP name [rootvg] +

# reorgvg rootvg
0516-962 reorgvg: Logical volume hd5 migrated.
0516-962 reorgvg: Logical volume hd9var migrated.
0516-962 reorgvg: Logical volume hd10opt migrated.
0516-962 reorgvg: Logical volume loglv00 migrated.
0516-962 reorgvg: Logical volume hd11admin migrated.
0516-962 reorgvg: Logical volume fslv00 migrated.
IBM Power Systems
Physical volumes
1
7
13
19
25
31
35
41
47
2
8
14
20
26
32
36
42
48
3
4
9
10
15
16
21
22
27
28
33
34
37
38
43
44
49
50
1
7
13
19
25
31
35
41
47
2
8
14
20
26
32
36
42
48
3
4
9
10
15
16
21
22
27
28
33
34
37
38
43
44
49
50
Logical storage

1 2 3 4 1 2 3 4
Logical
volume
Logical
partitions
Logical
volume
IBM Power Systems
LVM and RAID support
LVM supports the following three software RAID configurations:
RAID 0, Striping
RAID 1, Mirroring (up to 3 copies)
RAID 10 or 1 + 0, Striping + Mirroring

Striping aides performance, whereas mirroring aides availability.

In todays environment, most data resides in SANs. Disks in a SAN are
generally grouped together into a RAID array and divided into LUNs.
AIX sees LUNs as physical disks.
One should not further deploy AIX RAID configurations on top of H/W (SAN)
RAID configurations.
SAN environments provide greater levels of RAID support. (performance and
availability)
LUNs can be increased in size, if so AIX must know about it:
# chvg -g datavg

IBM Power Systems
LVM options which affect performance
Inter- and intra-policy
Logical volume placement on disk
Scheduling policy
Dictates how data is read/written for mirrored LVs
Mirror write consistency
Ensures mirrored PPs are consistent
Write verify
Verifies all writes with a read operation
Default is no. Generally it is not recommended to set to yes as it will
impact system (write) performance.

IBM Power Systems
Mirroring (RAID1)
Mirroring is when a logical partition maps to more than one
physical partition of the same volume group.

First copy
Second copy
Third copy
PP1
PP2
hdisk0
PP1
PP2
hdisk1
PP1
PP2
hdisk2
fslv00
LP1
LP2
IBM Power Systems
Mirroring, allocation
When mirroring, it is essential that all PP copies are stored on
different disks.
This setting is controlled by the Allocation policy.
Also referred to as strictness
Allocation can be set to:
No: Not recommended.
Yes (default): Will ensure no LP copies can share the same PV
Superstrict: Will ensure no LP copies can shares the same PV in an
LVM RAID 0 + 1 (10) configuration

IBM Power Systems
Striping (RAID 0)
Consecutive stripe units
are created on different
physical volumes.

Striping increases
read/write sequential
throughput by evenly
distributing stripe units
among disks.

Stripe unit size is specified
at the creation time.
4KB to 128MB
LP1
LP2
LP3
1
4
7
2
5 8
3
6
9
hdisk0
hdisk1
hdisk2
1
2
3
4
5
6
7
8
9
Stripe
Units
Stream of
data
IBM Power Systems
Striping and mirroring (RAID 10 or 1+0)
1
3
5
2
4 6
hdisk0
hdisk1
1
2
3
4
5
6
Stream of
data
1
3
5
2
4 6
hdisk2
hdisk3
Meets performance and high availability requirements
More expensive (requires more disks, minimum 4)
Mirroring allocation is automatically set to superstrict

IBM Power Systems
Logical volume placement
Intra-physical volume allocation policy

Inter-physical volume allocation policy
Minimum (default)
1 LV copy. One (or minimum) PV should contain all PPs
2 or 3 LV copies. Use as many PVs as copies, keeping PV usage down
to a minimum.
Maximum
PPs should be spread over as many PVs as possible.

Edge
Middle Inner-edge
Inner-middle
Center
Note: These settings have little effect when used in SAN environments, whereby
LUNs are in RAID configurations.
IBM Power Systems
Mirroring scheduling policy
Scheduling policies when mirroring:
Parallel (default)
Write operations on different physical partitions start at the same time.
When the longest write finishes, the write operation is complete.
Improves performance (especially RAID-Performance)
Parallel write/sequential read
> Primary copy is read first, I f unsuccessful, the next copy is used.
Parallel write/round robin read
> Round-robin reads alternate disks between copies.

Sequential
Second physical write operation is not started unless the first operation
has completed successfully.
In case of a total disk failure, there is always a good copy.
Increased availability, but decreases performance

IBM Power Systems
Mirror write consistency
Problem: If the system crashes before the write to all mirrors
is complete, the mirrors are in an inconsistent state, and the
system must distinguish between the old copy and the new
copy.

Solution: Mirror Write Consistency
Ensures PPs are consistent after reboot
Three modes: off, active, and passive
Active (default)
Uses a cache on disk
The physical write operation proceeds when the cache has been
updated.
Passive. (Big VGs only)
Logging of LV updates, but does not log writes
If the system crashes on reboot, a forced synchronization of the LVs
takes place.

IBM Power Systems
SMIT logical volume menu
# smit lv

Logical Volumes


List All Logical Volumes by Volume Group
Add a Logical Volume
Set Characteristic of a Logical Volume
Show Characteristics of a Logical Volume
Remove a Logical Volume
Copy a Logical Volume

IBM Power Systems
Adding a logical volume
# smit mklv
Add a Logical Volume

[Entry Fields]
Logical volume NAME [datalv]
* VOLUME GROUP name datavg
* Number of LOGICAL PARTITIONS [100] #
PHYSICAL VOLUME names [hdisk2 hdisk3] +
Logical volume TYPE [jfs2] +
POSITION on physical volume middle +
RANGE of physical volumes minimum +
MAXIMUM NUMBER of PHYSICAL VOLUMES [] #
to use for allocation
Number of COPIES of each logical 2 +
partition
Mirror Write Consistency? active +
Allocate each logical partition copy yes +
on a SEPARATE physical volume?
RELOCATE the logical volume during yes +
reorganization?
Logical volume LABEL []
MAXIMUM NUMBER of LOGICAL PARTITIONS [512] #
Enable BAD BLOCK relocation? yes +
SCHEDULING POLICY for writing/reading parallel +
logical partition copies
Enable WRITE VERIFY? no +
File containing ALLOCATION MAP []
Stripe Size? [Not Striped] +
Serialize IO? no +
mklv y datalv t jfs2 c 2 \
datavg 10 hdisk2 hdisk3
IBM Power Systems
Show LV characteristics (1 of 2)
# lslv -l datalv
datalv:N/A
PV COPIES IN BAND DISTRIBUTION
hdisk2 010:000:000 100% 000:010:000:000:000
hdisk3 010:000:000 100% 000:010:000:000:000

# lslv datalv
LOGICAL VOLUME: datalv VOLUME GROUP: datavg
LV IDENTIFIER: 00cf2e7f00004c000000011d68130bea.1
PERMISSION: read/write
VG STATE: active/complete LV STATE: closed/syncd
TYPE: jfs2 WRITE VERIFY: off
MAX LPs: 512 PP SIZE: 4 megabyte(s)
COPIES: 2 SCHED POLICY: parallel
LPs: 10 PPs: 20
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 1
MOUNT POINT: N/A LABEL: None
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes (superstrict)
IBM Power Systems
Show LV characteristics (2 of 2)
# lslv -m datalv
datalv:N/A
LP PP1 PV1 PP2 PV2 PP3 PV3
0001 0104 hdisk2 0104 hdisk3
0002 0105 hdisk2 0105 hdisk3
0003 0106 hdisk2 0106 hdisk3
0004 0107 hdisk2 0107 hdisk3
0005 0108 hdisk2 0108 hdisk3
0006 0109 hdisk2 0109 hdisk3
0007 0110 hdisk2 0110 hdisk3
0008 0111 hdisk2 0111 hdisk3
0009 0112 hdisk2 0112 hdisk3
0010 0113 hdisk2 0113 hdisk3

Show LP to PP relationship on disks

IBM Power Systems
Add copies to a logical volume
# smit mklvcopy

Add Copies to a Logical Volume


[Entry Fields]
* LOGICAL VOLUME name datalv
* NEW TOTAL number of logical partition 3 +
copies
PHYSICAL VOLUME names [hdisk4] +
MAXIMUM NUMBER of PHYSICAL VOLUMES [1] #
SYNCHRONIZE the data in the new yes +
logical partition copies?

mklvcopy -k datalv 3 hdisk4
IBM Power Systems
Increasing the size of a logical volume
# smit extendlv

Increase the Size of a Logical Volume


[Entry Fields]
* LOGICAL VOLUME name datalv
* Number of ADDITIONAL logical partitions [20] #
PHYSICAL VOLUME names [] +
MAXIMUM NUMBER of PHYSICAL VOLUMES [1] #

extendlv datalv 20
IBM Power Systems
Remove a logical volume
# smit rmlv

Remove a Logical Volume


[Entry Fields]
LOGICAL VOLUME name [datalv2] +
rmlv f datalv2
IBM Power Systems
List all logical volumes by volume group
# lsvg -o | lsvg -i l

datavg:
datalv jfs2 30 90 3 closed/syncd N/A
rootvg:
hd5 boot 1 1 1 closed/syncd N/A
hd6 paging 8 8 1 open/syncd N/A
hd8 jfslog 1 1 1 open/syncd N/A
hd4 jfs 15 15 1 open/syncd /
hd2 jfs 35 35 1 open/syncd /usr
hd9var jfs 5 5 1 open/syncd /var
hd3 jfs 3 3 1 open/syncd /tmp
hd1 jfs 1 1 1 open/syncd /home
hd10opt jfs 4 4 1 open/syncd /opt
loglv00 jfs2log 1 1 1 closed/syncd N/A
hd11admin jfs 2 2 1 open/syncd /admin
fslv00 jfs2 2 2 1 closed/syncd /db2

IBM Power Systems
Mirroring volume groups
Mirroring rootvg is very important.
Mirror a Volume Group


[Entry Fields]
* VOLUME GROUP name rootvg
Mirror sync mode [Foreground] +
PHYSICAL VOLUME names [hdisk1] +
Number of COPIES of each logical 2 +
partition
Keep Quorum Checking On? no +
Create Exact LV Mapping? no +

# smit mirrorvg

mirrorvg rootvg hdisk1
# bosboot -a -d /dev/hdisk1

# bootlist -m normal hdisk0 hdisk1

# shutdown Fr (not required with AIX6 and later)

Can be used to
mirror any VG
Additional steps
required for
rootvg
IBM Power Systems
Physical volumes
Volume group

Physical volume (PV)
Hard disk, a virtual disk or a LUN
Physical partition (PP)
Smallest assignable unit of allocation on a physical disk
1
7
13
19
25
31
35
41
47
2
8
14
20
26
32
36
42
48
3
4
9
10
15
16
21
22
27
28
33
34
37
38
43
44
49
50
1
7
13
19
25
31
35
41
47
2
8
14
20
26
32
36
42
48
3
4
9
10
15
16
21
22
27
28
33
34
37
38
43
44
49
50
Physical partitions
PV1
PV2
IBM Power Systems
SMIT physical volumes menu
# smit pv

Physical Volumes


List All Physical Volumes in System
Add a Disk
Change Characteristics of a Physical Volume
List Contents of a Physical Volume
Move Contents of a Physical Volume

IBM Power Systems
List physical volume information
# lspv
hdisk0 00cf2e7ff02c5fc4 rootvg active
hdisk1 00cf2e7f713ca357 None
hdisk2 00cf2e7fea693331 datavg active
hdisk3 00cf2e7fea6a26e0 datavg active
hdisk4 00cf2e7fea6a318 datavg active
# lspv hdisk3
PHYSICAL VOLUME: hdisk3 VOLUME GROUP: datavg
PV IDENTIFIER: 00cf2e7fea6a26e0
VG IDENTIFIER 00cf2e7f00004c000000011d68130bea
PV STATE: active
STALE PARTITIONS: 0 ALLOCATABLE: yes
PP SIZE: 4 megabyte(s) LOGICAL VOLUMES: 1
TOTAL PPs: 511 (2044 megabytes) VG DESCRIPTORS: 1
FREE PPs: 481 (1924 megabytes) HOT SPARE: no
USED PPs: 30 (120 megabytes) MAX REQUEST: 256K
FREE DISTRIBUTION: 103..72..102..102..102
USED DISTRIBUTION: 00..30..00..00..00
List all physical volumes in the system.

List the attributes of a PV.

IBM Power Systems
List logical volumes on a physical volume
# lspv -l hdisk0
hdisk0:
LV NAME LPs PPs DISTRIBUTION MOUNT POINT
hd2 35 35 00..00..03..20..12 /usr
hd9var 5 5 00..05..00..00..00 /var
hd8 1 1 00..00..01..00..00 N/A
hd4 15 15 00..00..15..00..00 /
hd5 1 1 01..00..00..00..00 N/A
hd6 8 8 00..08..00..00..00 N/A
hd10opt 4 4 04..00..00..00..00 /opt
hd3 3 3 00..03..00..00..00 /tmp
hd1 1 1 00..01..00..00..00 /home
hd11admin 2 2 00..02..00..00..00 /admin
fslv00 2 2 02..00..00..00..00 /db2
loglv00 1 1 00..01..00..00..00 N/A
IBM Power Systems
List a physical volume partition map
# lspv -p hdisk0
hdisk0:
PP RANGE STATE REGION LV NAME TYPE MOUNT POINT
1-1 used outer edge hd5 boot N/A
2-14 free outer edge
15-16 used outer edge fslv00 jfs2 /db2
17-20 used outer edge hd10opt jfs2 /opt
21-28 used outer middle hd6 paging N/A
29-29 used outer middle loglv00 jfs2log N/A
30-31 used outer middle hd11admin jfs2 /admin
32-32 used outer middle hd1 jfs2 /home
33-35 used outer middle hd3 jfs2 /tmp
36-40 used outer middle hd9var jfs2 /var
41-41 used center hd8 jfslog N/A
42-56 used center hd4 jfs2 /
57-59 used center hd2 jfs2 /usr
60-79 used inner middle hd2 jfs2 /usr
80-91 used inner edge hd2 jfs2 /usr
92-99 free inner edge
IBM Power Systems
Add or move contents of physical volumes
Today, virtually all disks are configured to AIX through
configuration manager (cfgmgr).

Move the contents of a physical volume:

migratepv [ -l lvname ] sourcePV targetPV ..
# migratepv -l lv02 hdisk0 hdisk6
IBM Power Systems
Documenting the disk storage setup
List the volume groups:
# lsvg

List the disks on the system (PVID and volume group):
# lspv

List which logical volumes are contained in each volume
group:
# lsvg -l vgname

List the logical volumes on each disk:
# lspv -l pvname

IBM Power Systems
Checkpoint
1. True or False: A logical volume can span more than one
physical volume.
volume group.
3. True or False: The contents of a physical volume can be
divided between two volume groups.
4. True or False: If mirroring logical volumes, it is not necessary
to perform a backup.
5. True or False: SMIT can be used to easily increase or decrease
the size of an enhanced JFS filesystem.
6. True or False: Striping can be combined with mirroring to
provide increased performance and availability.
IBM Power Systems
Checkpoint solutions
physical volume.
volume group.
3. True or False: The contents of a physical volume can be
divided between two volume groups.
4. True or False: If mirroring logical volumes, it is not
necessary to perform a backup. False. You still need to
back up to external media.
5. True or False: SMIT can be used to easily increase or
decrease the size of an enhanced JFS filesystem.
6. True or False: Striping can be combined with mirroring to
provide increased performance and availability
IBM Power Systems
Exercise 8
Working with LVM
IBM Power Systems
Unit summary
Having completed this unit, you should be able to:

Explain how to work with the Logical Volume Manager
Add, change, and delete:
Volume groups
Logical volumes
Physical volumes
Describe essential LVM concepts, such as:
Mirroring
Striping

AN121 G 08

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AN121 G 08

Uploaded by

Copyright:

Available Formats

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

You might also like