Working With The Logical Volume Manager

Working with the Logical Volume
Manager
© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

US Government Users Restricted Rights - Use duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp 8.1
Unit objectives
IBM Power Systems
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

US Government Users Restricted Rights - Use duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp
Logical Volume Manager
IBM Power Systems
# smit lvm
Logical
Logical Volume
Volume Manager
Manager
Move
Move cursor
cursor to
to desired
desired item
item and
and press
press Enter.
Enter.
Volume
Volume Groups
Groups
Logical
Logical Volumes
Volumes
Physical
Physical Volumes
Volumes
Paging
Paging Space
Space

SMIT Volume Groups menu
IBM Power Systems
Volume
Volume Groups
Groups
Move
Move cursor
cursor to
to desired
desired item
item and
and press
press Enter.
Enter.
List
List All
All Volume
Volume Groups
Groups
Add
Add a Volume Group
a Volume Group
Set
Set Characteristics
Characteristics of of aa Volume
Volume Group
Group
List
List Contents of a Volume Group
Contents of a Volume Group
Remove
Remove aa Volume
Volume Group
Group
Activate
Activate a Volume
a Volume Group
Group
Deactivate
Deactivate aa Volume
Volume Group
Group
Import
Import aa Volume
Volume Group
Group
Export
Export aa Volume
Volume Group
Group
Mirror
Mirror aa Volume
Volume Group
Group
Unmirror
Unmirror aa Volume
Volume Group
Group
Synchronize
Synchronize LVM LVM Mirrors
Mirrors
Back
Back UpUp aa Volume
Volume Group
Group
Remake
Remake a Volume Group
a Volume Group
Preview
Preview Information
Information about
about aa Backup
Backup
Verify
Verify the Readability of
the Readability of aa Backup
Backup (Tape
(Tape only)
only)
View the Backup
View the Backup Log Log
List
List Files
Files inin aa Volume
Volume Group
Group Backup
Backup
Restore
Restore Files in a Volume Group
Files in a Volume Group Backup
Backup
Adding a volume group to the system
IBM Power Systems
# smit mkvg mkvg –y datavg hdisk1 hdisk2

Add
Add aa Volume
Volume Group
Group
Move
Move cursor
cursor to
to desired
desired item
item and
and press
press Enter.
Enter.
Add
Add an
an Original
Original Volume
Volume Group
Group
Add
Add aa Big Volume Group
Big Volume Group
Add
Add aa Scalable
Scalable Volume
Volume Group
Group
Add
Add an
an Original
Original Volume
Volume Group
Group
[Entry
[Entry Fields]
Fields]
VOLUME
VOLUME GROUP
GROUP name
name [datavg]
[datavg]
Physical
Physical partition
partition SIZE
SIZE in
in megabytes
megabytes ++
** PHYSICAL
PHYSICAL VOLUME
VOLUME names
names [hdisk1
[hdisk1 hdisk2]
hdisk2] ++
Force
Force the
the creation
creation of
of aa volume
volume group?
group? no
no ++
Activate
Activate volume
volume group
group AUTOMATICALLY
AUTOMATICALLY yes
yes ++
at
at system
system restart?
restart?
Volume
Volume Group
Group MAJOR
MAJOR NUMBER
NUMBER []
[] +#
+#
Create
Create VG
VG Concurrent
Concurrent Capable?
Capable? no
no ++

Adding a scalable volume group to the system
IBM Power Systems
# smit mkvg mkvg –S –y db2_vg hdisk3
Add
Add aa Scalable
Scalable Volume
Volume Group
Group
Type
Type or
or select
select values
values in
in entry
entry fields.
fields.
Press
Press Enter
Enter AFTER
AFTER making
making all
all desired
desired changes.
changes.
[Entry
[Entry Fields]
Fields]
VOLUME
VOLUME GROUP
GROUP name
name [db2_vg]
[db2_vg]
Physical
Physical partition
partition SIZE
SIZE in
in megabytes
megabytes ++
** PHYSICAL VOLUME names
PHYSICAL VOLUME names [hdisk3]
[hdisk3] ++
Force
Force the
the creation
creation of
of aa volume
volume group?
group? no
no ++
Activate volume group AUTOMATICALLY
Activate volume group AUTOMATICALLY yes
yes ++
at
at system
system restart?
restart?
Volume
Volume Group
Group MAJOR
MAJOR NUMBER
NUMBER []
[] +#
+#
Create
Create VG Concurrent Capable?
VG Concurrent Capable? no
no ++
Max
Max PPs
PPs per
per VG
VG in
in units
units of
of 1024
1024 32
32 ++
Max
Max Logical
Logical Volumes
Volumes 256
256 ++
Enable
Enable Strict
Strict Mirror
Mirror Pools
Pools No
No ++
Infinite
Infinite Retry
Retry Option
Option no
no ++

Listing volume groups and VG attributes
IBM Power Systems
## lsvg
lsvg
rootvg
rootvg
datavg
datavg
db2_vg
db2_vg
## lsvg
lsvg -o
-o
datavg
datavg
rootvg
rootvg
## lsvg
lsvg rootvg
rootvg
VOLUME
VOLUME GROUP:
GROUP: rootvg
rootvg VG
VG IDENTIFIER:
IDENTIFIER:
00cf2e7f00004c000000011cec07b52e
00cf2e7f00004c000000011cec07b52e
VG
VG STATE:
STATE: active
active PP
PP SIZE:
SIZE: 64
64 megabyte(s)
megabyte(s)
VG
VG PERMISSION:
PERMISSION: read/write
read/write TOTAL
TOTAL PPs:
PPs: 130
130 (8320
(8320 megabytes)
megabytes)
MAX
MAX LVs:
LVs: 256
256 FREE
FREE PPs:
PPs: 54
54 (3456 megabytes)
(3456 megabytes)
LVs:
LVs: 11
11 USED
USED PPs:
PPs: 76
76 (4864
(4864 megabytes)
megabytes)
OPEN
OPEN LVs:
LVs: 99 QUORUM:
QUORUM: 22 (Enabled)
(Enabled)
TOTAL
TOTAL PVs:
PVs: 22 VG
VG DESCRIPTORS:
DESCRIPTORS: 33
STALE
STALE PVs:
PVs: 00 STALE
STALE PPs:
PPs: 00
ACTIVE
ACTIVE PVs:
PVs: 22 AUTO
AUTO ON:
ON: yes
yes
MAX
MAX PPs
PPs per
per VG:
VG: 32512
32512
MAX PPs per PV:
MAX PPs per PV: 1016
1016 MAX
MAX PVs:
PVs: 32
32
LTG
LTG size
size (Dynamic):
(Dynamic): 256
256 kilobyte(s)
kilobyte(s) AUTO
AUTO SYNC:
SYNC: no
no
HOT
HOT SPARE:
SPARE: no
no BB
BB POLICY:
POLICY: relocatable
relocatable

Listing PVs in a VG and VG contents
IBM Power Systems
## lsvg
lsvg -p
-p rootvg
rootvg
rootvg:
rootvg:
PV_NAME
PV_NAME PV
PV STATE
STATE TOTAL
TOTAL PPs
PPs FREE
FREE PPs
PPs FREE
FREE DISTRIBUTION
DISTRIBUTION
hdisk0
hdisk0 active
active 99
99 23
23 15..00..00..00..08
15..00..00..00..08
hdisk5
hdisk5 active
active 31
31 31
31 07..06..06..06..06
07..06..06..06..06
## lsvg
lsvg -l-l rootvg
rootvg
rootvg:
rootvg:
LV
LV NAME
NAME TYPE
TYPE LPs
LPs PPs
PPs PVs
PVs LV
LV STATE
STATE MOUNT
MOUNT
POINT
POINT
hd5
hd5 boot
boot 11 11 11 closed/syncd
closed/syncd N/A
N/A
hd6
hd6 paging
paging 88 88 11 open/syncd
open/syncd N/A
N/A
hd8
hd8 jfslog
jfslog 11 11 11 open/syncd
open/syncd N/A
N/A
hd4
hd4 jfs
jfs 15
15 15
15 11 open/syncd
open/syncd //
hd2
hd2 jfs
jfs 35
35 35
35 11 open/syncd
open/syncd /usr
/usr
hd9var
hd9var jfs
jfs 55 55 11 open/syncd
open/syncd /var
/var
hd3
hd3 jfs
open/syncd /tmp
/tmp
hd1
hd1 jfs
open/syncd /home
/home
hd10opt
hd10opt jfs
open/syncd /opt
/opt

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

Remove a volume group
IBM Power Systems
# smit reducevg2 reducevg -df db2_vg hdisk2 hdisk3
Remove
Remove aa Volume
Volume Group
Group
Type
Type or
or select
select aa value
value for
for the
the entry
entry field.
field.
Press
Press Enter AFTER making all desired
Enter AFTER making all desired changes.
changes.
[Entry
[Entry Fields]
Fields]
** VOLUME
VOLUME GROUP
GROUP name
name [db2_vg]
[db2_vg] ++

Activate and Deactivate a Volume Group
IBM Power Systems
# smit varyonvg varyonvg datavg

Activate
Activate aa Volume
Volume Group
Group
[Entry
[Entry Fields]
Fields]
** VOLUME
VOLUME GROUP
GROUP name
name [datavg]
[datavg] ++
RESYNCHRONIZE
RESYNCHRONIZE stale
stale physical
physical partitions?
partitions? yes
yes ++
Activate
Activate volume
volume group
group in
in SYSTEM
SYSTEM no
no ++
MANAGEMENT
MANAGEMENT mode?
mode?
FORCE
FORCE activation
activation of of the
the volume
volume group?
group? no
no ++
Warning--this
Warning--this may cause loss of data
may cause loss of data integrity.
integrity.
Varyon VG in Concurrent
Varyon VG in Concurrent Mode?Mode? no
no ++
Synchronize
Synchronize Logical
Logical Volumes?
Volumes? no
no ++
# smit varyoffvg varyoffvg datavg
Deactivate
Deactivate aa Volume
Volume Group
Group
[Entry
[Entry Fields]
Fields]
** VOLUME
VOLUME GROUP
GROUP name
name [datavg]
[datavg] ++
Put
Put volume group
volume group in
in SYSTEM
SYSTEM no
no ++
MANAGEMENT mode?
MANAGEMENT mode?
Import and Export a Volume Group
IBM Power Systems
# smit importvg importvg –y datavg hdisk3

Import
Import aa Volume
Volume Group
Group
[Entry
[Entry Fields]
Fields]
VOLUME
VOLUME GROUP
GROUP name
name [datavg]
[datavg]
** PHYSICAL
PHYSICAL VOLUME name
VOLUME name [hdisk3]
[hdisk3] ++
Volume
Volume Group
Group MAJOR
MAJOR NUMBER
NUMBER []
[] +#
+#
# smit exportvg exportvg datavg
Export
Export aa Volume
Volume Group
Group
[Entry
[Entry Fields]
Fields]
** VOLUME
VOLUME GROUP
GROUP name
name [datavg]
[datavg] ++
Note: The volume group must be inactive before it is exported.

Logical storage
IBM Power Systems
Physical volumes
1 4 1 4
7 2 3 7 2 3
10 10
8 9 8 9
13 16 13 16
14 15 19 14 15
19 22 22
20 21 25 20 21
25 28 28
26 27 31 26 27
31 34 34
32 33 32 33
35 38 35 38
36 37 41 36 37
41 44 44
42 43 42 43
47 50 47 50
48 49 48 49
Logical Volume Manager
1 2 3 4 1 2 3 4 Logical
partitions
Logical Logical
volume volume
LVM and RAID support
IBM Power Systems
• 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 today’s 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
LVM options which affect performance
IBM Power Systems
• 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.

Mirroring (RAID1)
IBM Power Systems
• Mirroring is when a logical partition maps to more than one

physical partition of the same volume group.
hdisk0 fslv00
First copy PP1
PP2 LP1
LP2
hdisk1
Second copy PP1
PP2
hdisk2
Third copy PP1
PP2

Mirroring, allocation
IBM Power Systems
• When mirroring, it is essential that all PP copies are stored on

different disks.
• This setting is controlled by the Allocation policy.

– This is also referred to as strictness.
• Allocation can be set to:

– No: This is not recommended.
– Yes (default): This ensures that no LP copies can share the same PV.
– Superstrict: Ensures that a given PV does not have a mixture of
primary and secondary copies, in addition to strictness.

Striping (RAID 0)
IBM Power Systems
• Consecutive stripe units are

created on different physical
1 4 7 LP1 volumes.
1
Stripe hdisk0 2 • Striping increases read/write
units 3 sequential throughput by
LP2 4 evenly distributing stripe units
2
5 8 among disks.
5
6
hdisk1 • Stripe unit size is specified at
7 the creation time.
8 – 4 KB to 128 MB
3 6 9
LP3 9
Stream of
data
hdisk2
Striping and mirroring (RAID 10 or 1+0)
IBM Power Systems
1 3 5 1 3 5 1
2
hdisk2 hdisk0 3
4
2
5
2 4 6 4 6
6
Stream of
hdisk3 hdisk1 data
• Meets performance and high availability requirements

• More expensive (requires more disks, minimum four)
• Mirroring allocation automatically set to superstrict

Mirror pools
IBM Power Systems
• Mirror pools simplify the task of isolating a logical volume

copy to a specific group of physical volumes.
hdisk0
PP1
First copy PP3
on PoolA
hdisk1 lv00
PP2
PoolB hdisk PP4 LP1
should be on LP2
remote storage LP3
server!
hdisk2 LP4
PP1
PP3
Second copy
on PoolB hdisk3
PP2
PP4

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

Middle Inner-edge
Center Inner-middle
Edge
• 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.
Note: These settings have little effect when used in SAN environments, whereby
LUNs are in RAID configurations.
Mirroring scheduling policy
IBM Power Systems
• 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

Mirror write consistency
IBM Power Systems
• 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.

SMIT Logical Volumes menu
IBM Power Systems
# smit lv
Logical
Logical Volumes
Volumes
Move
Move cursor
cursor to
to desired
desired item
item and
and press
press Enter.
Enter.
List
List All
All Logical
Logical Volumes
Volumes byby Volume
Volume Group
Group
Add
Add aa Logical
Logical Volume
Volume
Set
Set Characteristic
Characteristic of
of aa Logical
Logical Volume
Volume
Show
Show Characteristics of a Logical
Characteristics of a Logical Volume
Volume
Remove
Remove aa Logical
Logical Volume
Volume
Copy
Copy aa Logical
Logical Volume
Volume

Add a Logical Volume
IBM Power Systems
mklv –y datalv –t jfs2 –c 2 \
# smit mklv datavg 10 hdisk2 hdisk3
Add
Add aa Logical
Logical Volume
Volume
[Entry
[Entry Fields]
Fields]
Logical
Logical volume
volume NAME
NAME [datalv]
[datalv]
** VOLUME
VOLUME GROUP
GROUP name
name datavg
datavg
** Number
Number of
of LOGICAL
LOGICAL PARTITIONS
PARTITIONS [100]
[100] ##
PHYSICAL
PHYSICAL VOLUME
VOLUME names
names [hdisk2
[hdisk2 hdisk3]
hdisk3] ++
Logical
Logical volume
volume TYPE
TYPE [jfs2]
[jfs2] ++
POSITION
POSITION onon physical
physical volume
volume middle
middle ++
RANGE
RANGE of
of physical
physical volumes
volumes minimum
minimum ++
MAXIMUM
MAXIMUM NUMBER
NUMBER of of PHYSICAL
PHYSICAL VOLUMES
VOLUMES []
[] ##
to
to use
use for
for allocation
allocation
Number of COPIES of each logical
Number of COPIES of each logical 22 ++
partition
partition
Mirror
Mirror Write
Write Consistency?
Consistency? active
active ++
Allocate
Allocate each
each logical
logical partition
partition copy
copy yes
yes ++
on
on a SEPARATE physical
a SEPARATE physical volume?
volume?
RELOCATE the logical volume
RELOCATE the logical volume duringduring yes
yes ++
reorganization?
reorganization?
Logical
Logical volume
volume LABEL
LABEL []
[]
MAXIMUM
MAXIMUM NUMBER
NUMBER of of LOGICAL
LOGICAL PARTITIONS
PARTITIONS [512]
[512] ##
Enable
Enable BAD BLOCK relocation?
BAD BLOCK relocation? yes
yes ++
SCHEDULING POLICY for writing/reading
SCHEDULING POLICY for writing/reading parallel
parallel ++
logical
logical partition
partition copies
copies
Enable
Enable WRITE
WRITE VERIFY?
VERIFY? no
no ++
File
File containing ALLOCATION MAP
containing ALLOCATION MAP []
[]
Stripe
Stripe Size?
Size? [Not
[Not Striped]
Striped] ++
Serialize IO?
Serialize IO? no
no ++
Mirror
Mirror Pool
Pool for
for First
First Copy
Copy ++
Mirror
Mirror Pool
Pool for
for Second
Second Copy
Copy ++
Mirror Pool for Third
Mirror Pool for Third Copy Copy ++
Infinite Retry Option
Infinite Retry Option no
no ++

Show LV characteristics (1 of 2)
IBM Power Systems
## lslv
lslv datalv
datalv
LOGICAL
LOGICAL VOLUME:
VOLUME: datalv
datalv VOLUME
VOLUME GROUP:
GROUP: datavg
datavg
LV
LV IDENTIFIER:
IDENTIFIER: 00cf2e7f00004c000000011d68130bea.1
00cf2e7f00004c000000011d68130bea.1
PERMISSION:
PERMISSION: read/write
read/write
VG
VG STATE:
STATE: active/complete
active/complete LV
LV STATE:
STATE: closed/syncd
closed/syncd
TYPE:
TYPE: jfs2
jfs2 WRITE
WRITE VERIFY:
VERIFY: off
off
MAX
MAX LPs:
LPs: 512
512 PP
PP SIZE:
SIZE: 44 megabyte(s)
megabyte(s)
COPIES:
COPIES: 22 SCHED
SCHED POLICY:
POLICY: parallel
parallel
LPs:
LPs: 10
10 PPs:
PPs: 20
20
STALE
STALE PPs:
PPs: 00 BB
BB POLICY:
POLICY: relocatable
relocatable
INTER-POLICY:
INTER-POLICY: minimum
minimum RELOCATABLE:
RELOCATABLE: yes
yes
INTRA-POLICY:
INTRA-POLICY: middle
middle UPPER
UPPER BOUND:
BOUND: 11
MOUNT
MOUNT POINT:
POINT: N/A
N/A LABEL:
LABEL: None
None
MIRROR
MIRROR WRITE
WRITE CONSISTENCY:
CONSISTENCY: on/ACTIVE
on/ACTIVE
EACH
EACH LPLP COPY
COPY ON
ON AA SEPARATE
SEPARATE PV
PV ?:
?: yes
yes (superstrict)
(superstrict)
Serialize
Serialize IO IO ?:
?: NO
NO
INFINITE
INFINITE RETRY:
RETRY: no
no
DEVICESUBTYPE:
DEVICESUBTYPE: DS_LVZ
DS_LVZ
COPY
COPY 11 MIRROR
MIRROR POOL:
POOL: None
None
COPY
COPY 22 MIRROR
MIRROR POOL:
POOL: None
None
COPY
COPY 33 MIRROR
MIRROR POOL:
POOL: None
None
## lslv
lslv -l
-l datalv
datalv
datalv:N/A
datalv:N/A
PV
PV COPIES
COPIES IN
IN BAND
BAND DISTRIBUTION
DISTRIBUTION
hdisk2
hdisk2 010:000:000
010:000:000 100%
100% 000:010:000:000:000
000:010:000:000:000
hdisk3
hdisk3 010:000:000
010:000:000 100%
100% 000:010:000:000:000
000:010:000:000:000
Show LV characteristics (2 of 2)
IBM Power Systems
• Show LP to PP relationship on disks

## lslv
lslv -m
-m datalv
datalv
datalv:N/A
datalv:N/A
LP
LP PP1
PP1 PV1
PV1 PP2
PP2 PV2
PV2 PP3
PP3 PV3
PV3
0001
0001 0104
0104 hdisk2
hdisk2 0104
0104 hdisk3
hdisk3
0002
0002 0105
0105 hdisk2
hdisk2 0105
0105 hdisk3
hdisk3
0003 0106 hdisk2
0003 0106 hdisk2 0106
0106 hdisk3
hdisk3
0004
0004 0107
0107 hdisk2
hdisk2 0107
0107 hdisk3
hdisk3
0005
0005 0108 hdisk2
0108 hdisk2 0108
0108 hdisk3
hdisk3
0006
0006 0109
0109 hdisk2
hdisk2 0109
0109 hdisk3
hdisk3
0007
0007 0110
0110 hdisk2
hdisk2 0110
0110 hdisk3
hdisk3
0008
0008 0111
0111 hdisk2
hdisk2 0111
0111 hdisk3
hdisk3
0009
0009 0112
0112 hdisk2
hdisk2 0112
0112 hdisk3
hdisk3
0010
0010 0113
0113 hdisk2
hdisk2 0113
0113 hdisk3
hdisk3

Reorganize logical volumes in a volume group
IBM Power Systems
• reorgvg moves physical partition allocations for logical

volumes to more closely match the policies of those LVs.
hdisk3 hdisk4
datavg
1 2 3 4
empty
5 6 7 8
• # chlv –e x mylv (set to maximum number of disks)

• # reorgvg datavg mylv
hdisk3 hdisk4
datavg
1 3 5 7 2 4 6 8

Add Copies to a Logical Volume
IBM Power Systems
# smit mklvcopy mklvcopy -k datalv 3 hdisk4
Add
Add Copies
Copies to
to aa Logical
Logical Volume
Volume
Type
Type or
or select
select values
values in
in entry
entry fields.
fields.
Press
Press Enter AFTER making
Enter AFTER making all
all desired
desired changes.
changes.
[Entry
[Entry Fields]
Fields]
** LOGICAL
LOGICAL VOLUME
VOLUME name
name datalv
datalv
** NEW
NEW TOTAL
TOTAL number
number of
of logical
logical partition
partition 33 ++
copies
copies
PHYSICAL
PHYSICAL VOLUME
VOLUME names
names [hdisk4]
[hdisk4] ++
POSITION
physical volume
volume middle
middle ++
RANGE
RANGE ofof physical
physical volumes
volumes minimum
minimum ++
MAXIMUM
MAXIMUM NUMBER
NUMBER of
of PHYSICAL
PHYSICAL VOLUMES
VOLUMES [1]
[1] ##
to
to use
use for
for allocation
allocation
Allocate
Allocate each
each logical
logical partition
partition copy
copy yes
yes ++
on
on a SEPARATE physical volume?
File
File containing
containing ALLOCATION
ALLOCATION MAP
MAP []
[]
SYNCHRONIZE
SYNCHRONIZE the data in
the data in the
the new
new yes
yes ++
logical
logical partition
partition copies?
copies?
Mirror
Mirror Pool
Pool for
for First
First Copy
Copy []
[] ++
Mirror
Mirror Pool
Pool for
for Second
Second Copy
Copy []
[] ++
Mirror
Mirror Pool
Pool for
for Third
Third Copy
Copy []
[] ++

Increase the Size of a Logical Volume
IBM Power Systems
# smit extendlv extendlv datalv 20
Increase
Increase the
the Size
Size of
of aa Logical
Logical Volume
Volume
Type
Type or
or select
select values
values in
in entry
entry fields.
fields.
Press
all desired
desired changes.
changes.
[Entry
[Entry Fields]
Fields]
** LOGICAL
LOGICAL VOLUME
VOLUME name
name datalv
datalv
** Number
Number of ADDITIONAL
of ADDITIONAL logical
logical partitions
partitions [20]
[20] ##
PHYSICAL
PHYSICAL VOLUME
VOLUME names
names []
[] ++
POSITION
physical volume
volume middle
middle ++
RANGE
RANGE of physical volumes
of physical volumes minimum
minimum ++
MAXIMUM
MAXIMUM NUMBER
NUMBER of
of PHYSICAL
PHYSICAL VOLUMES
VOLUMES [1]
[1] ##
to
to use
use for
for allocation
allocation
Allocate
Allocate each
each logical
logical partition
partition copy
copy yes
yes ++
on
on a SEPARATE physical volume?
File
File containing
containing ALLOCATION
ALLOCATION MAP
MAP []
[]

Remove a Logical Volume
IBM Power Systems
# smit rmlv rmlv –f datalv2
Remove
Remove aa Logical
Logical Volume
Volume
Type
Type or
or select
select values
values in
in entry
entry fields.
fields.
Press
all desired
desired changes.
changes.
[Entry
[Entry Fields]
Fields]
LOGICAL
LOGICAL VOLUME
VOLUME name
name [datalv2]
[datalv2] ++

List all logical volumes by volume group
IBM Power Systems
## lsvg
lsvg -o
-o || lsvg
lsvg -i
-i –l
–l
datavg:
datavg:
LV
LV NAME
NAME TYPE
TYPE LPs
LPs PPs
PPs PVs
PVs LV
LV STATE
STATE MOUNT
MOUNT POINT
POINT
datalv
datalv jfs2
jfs2 30
30 90
90 33 closed/syncd
closed/syncd N/A
N/A
rootvg:
rootvg:
LV
LV NAME
NAME TYPE
TYPE LPs
LPs PPs
PPs PVs
PVs LV
LV STATE
STATE MOUNT
MOUNT POINT
POINT
hd5
hd5 boot
boot 11 11 11 closed/syncd
closed/syncd N/A
N/A
hd6
hd6 paging
paging 88 88 11 open/syncd
open/syncd N/A
N/A
hd8
hd8 jfslog
jfslog 11 11 11 open/syncd
open/syncd N/A
N/A
hd4
hd4 jfs
jfs 15
15 15
15 11 open/syncd
open/syncd //
hd2
hd2 jfs
jfs 35
35 35
35 11 open/syncd
open/syncd /usr
/usr
hd9var
hd9var jfs
open/syncd /var
/var
hd3
hd3 jfs
open/syncd /tmp
/tmp
hd1
hd1 jfs
open/syncd /home
/home
hd10opt
hd10opt jfs
open/syncd /opt
/opt
loglv00
loglv00 jfs2log
jfs2log 11 11 11 closed/syncd
closed/syncd N/A
N/A
hd11admin
hd11admin jfs
open/syncd /admin
/admin
fslv00
fslv00 jfs2
jfs2 22 22 11 closed/syncd
closed/syncd /db2
/db2

Mirroring volume groups
IBM Power Systems
• Mirroring rootvg is very important.

# smit mirrorvg mirrorvg rootvg hdisk1
Mirror Can be used
Mirror aa Volume
Volume Group
Group
to mirror
any VG
Type
Type or
or select
select values
values in
in entry
entry fields.
fields.
Press
Press Enter
Enter AFTER
AFTER making
making all
all desired
desired changes.
changes.
[Entry
[Entry Fields]
Fields]
** VOLUME
VOLUME GROUP
GROUP name
name rootvg
rootvg
Mirror
Mirror sync mode
sync mode [Foreground]
[Foreground] ++
PHYSICAL
PHYSICAL VOLUME
VOLUME names
names [hdisk1]
[hdisk1] ++
Number
Number of COPIES
of COPIES of
of each
each logical
logical 22 ++
partition
partition
Keep
Keep Quorum
Quorum Checking
Checking On?
On? no
no ++
Create
Create Exact LV
Exact LV Mapping?
Mapping? no
no ++
## bosboot
bosboot -a
-a -d
-d /dev/hdisk1
/dev/hdisk1
Additional
## bootlist
bootlist -m
-m normal
normal hdisk0
hdisk0 hdisk1
hdisk1 steps
required for
## shutdown rootvg
shutdown –Fr
–Fr (not
(not required
required with
with AIX6
AIX6 and
and later)
later)
Physical volumes
IBM Power Systems
PV1 Volume group PV2
1 1 4
4
2 2 3
7 3 7 10
10 8
8 9 9
13 13 16
16 14
14 15 19 15
19 22 22
20 20 21
25 21 25 28
28 26 27
26 27 31
31 34 34
32 32 33
35 33 35
38 38
36 36 37
41 37 41 44
44 42 43
42 43 47
47 50 50
48 49 48 49
Physical partitions
• Physical volume (PV)
– Hard disk, a virtual disk or a LUN
• Physical partition (PP)
– Smallest assignable unit of allocation on a physical disk
SMIT Physical Volumes menu
IBM Power Systems
# smit pv
Physical
Physical Volumes
Volumes
Move
Move cursor
cursor to
to desired
desired item
item and
and press
press Enter.
Enter.
List
List All
All Physical
Physical Volumes
Volumes in
in System
System
Add
Add aa Disk
Disk
Change
Change Characteristics
Characteristics ofof aa Physical
Physical Volume
Volume
List Contents of a Physical Volume
List Contents of a Physical Volume
Move
Move Contents
Contents of
of aa Physical
Physical Volume
Volume

List physical volume information
IBM Power Systems
• List all physical volumes in the system.

## lspv
lspv
hdisk0
hdisk0 00cf2e7ff02c5fc4
00cf2e7ff02c5fc4 rootvg
rootvg active
active
hdisk1
hdisk1 00cf2e7f713ca357
00cf2e7f713ca357 None
None
hdisk2
hdisk2 00cf2e7fea693331
00cf2e7fea693331 datavg
datavg active
active
hdisk3
hdisk3 00cf2e7fea6a26e0
00cf2e7fea6a26e0 datavg
datavg active
active
hdisk4
hdisk4 00cf2e7fea6a318
00cf2e7fea6a318 datavg
datavg active
active
• List the attributes of a PV.

## lspv
lspv hdisk3
hdisk3
PHYSICAL
PHYSICAL VOLUME:
VOLUME: hdisk3
hdisk3 VOLUME
VOLUME GROUP:
GROUP: datavg
datavg
PV
PV IDENTIFIER:
IDENTIFIER: 00cf2e7fea6a26e0
00cf2e7fea6a26e0
VG
VG IDENTIFIER
IDENTIFIER 00cf2e7f00004c000000011d68130bea
00cf2e7f00004c000000011d68130bea
PV
PV STATE:
STATE: active
active
STALE
STALE PARTITIONS:
PARTITIONS: 00 ALLOCATABLE:
ALLOCATABLE: yes
yes
PP
PP SIZE:
SIZE: 44 megabyte(s)
megabyte(s) LOGICAL
LOGICAL VOLUMES:
VOLUMES: 11
TOTAL
TOTAL PPs:
PPs: 511 (2044 megabytes)
511 (2044 megabytes) VG
VG DESCRIPTORS:
DESCRIPTORS: 11
FREE
FREE PPs:
PPs: 481
481 (1924
(1924 megabytes)
megabytes) HOT
HOT SPARE:
SPARE: no
no
USED
USED PPs:
PPs: 30
30 (120
(120 megabytes)
megabytes) MAX
MAX REQUEST:
REQUEST: 256K
256K
FREE
FREE DISTRIBUTION:
DISTRIBUTION: 103..72..102..102..102
103..72..102..102..102
USED
USED DISTRIBUTION:
DISTRIBUTION: 00..30..00..00..00
00..30..00..00..00
MIRROR
MIRROR POOL:
POOL: None
None
List logical volumes on a physical volume
IBM Power Systems
## lspv
lspv -l-l hdisk0
hdisk0
hdisk0:
hdisk0:
LV
LV NAME
NAME LPs
LPs PPs
PPs DISTRIBUTION
DISTRIBUTION MOUNT
MOUNT POINT
POINT
hd2
hd2 35
35 35
35 00..00..03..20..12
00..00..03..20..12 /usr
/usr
hd9var
hd9var 55 55 00..05..00..00..00
00..05..00..00..00 /var
/var
hd8
hd8 11 11 00..00..01..00..00
00..00..01..00..00 N/A
N/A
hd4
hd4 15
15 15
15 00..00..15..00..00
00..00..15..00..00 //
hd5
hd5 11 11 01..00..00..00..00
01..00..00..00..00 N/A
N/A
hd6
hd6 88 88 00..08..00..00..00
00..08..00..00..00 N/A
N/A
hd10opt
hd10opt 44 44 04..00..00..00..00
04..00..00..00..00 /opt
/opt
hd3
hd3 33 33 00..03..00..00..00
00..03..00..00..00 /tmp
/tmp
hd1
hd1 11 11 00..01..00..00..00
00..01..00..00..00 /home
/home
hd11admin
hd11admin 22 22 00..02..00..00..00
00..02..00..00..00 /admin
/admin
fslv00
fslv00 22 22 02..00..00..00..00
02..00..00..00..00 /db2
/db2
loglv00
loglv00 11 11 00..01..00..00..00
00..01..00..00..00 N/A
N/A

List a physical volume partition map
IBM Power Systems
## lspv
lspv -p
-p hdisk0
hdisk0
hdisk0:
hdisk0:
PP
PP RANGE
RANGE STATE
STATE REGION
REGION LV
LV NAME
NAME TYPE
TYPE MOUNT
MOUNT
POINT
POINT
1-1
1-1 used
used outer
outer edge
edge hd5
hd5 boot
boot N/A
N/A
2-14
2-14 free
free outer
outer edge
edge
15-16
15-16 used
used outer
outer edge
edge fslv00
fslv00 jfs2
jfs2 /db2
/db2
17-20
17-20 used
used outer edge
outer edge hd10opt
hd10opt jfs2
jfs2 /opt
/opt
21-28
21-28 used
used outer
outer middle
middle hd6
hd6 paging
paging N/A
N/A
29-29
29-29 used
used outer
outer middle
middle loglv00
loglv00 jfs2log
jfs2log N/A
N/A
30-31
30-31 used
used outer
outer middle
middle hd11admin
hd11admin jfs2
jfs2 /admin
/admin
32-32
32-32 used
used outer
outer middle
middle hd1
hd1 jfs2
jfs2 /home
/home
33-35
33-35 used
used outer
outer middle
middle hd3
hd3 jfs2
jfs2 /tmp
/tmp
36-40
36-40 used
used outer
outer middle
middle hd9var
hd9var jfs2
jfs2 /var
/var
41-41
41-41 used
used center
center hd8
hd8 jfslog
jfslog N/A
N/A
42-56
42-56 used
used center
center hd4
hd4 jfs2
jfs2 //
57-59
57-59 used
used center
center hd2
hd2 jfs2
jfs2 /usr
/usr
60-79
60-79 used
used inner
inner middle
middle hd2
hd2 jfs2
jfs2 /usr
/usr
80-91
80-91 used
used inner
inner edge
edge hd2
hd2 jfs2
jfs2 /usr
/usr
92-99
92-99 free
free inner
inner edge
edge

Add or move contents of physical volumes
IBM Power Systems
• 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
migratepv -l
-l lv02
lv02 hdisk0
hdisk0 hdisk6
hdisk6

Documenting the disk storage setup
IBM Power Systems
• 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
Checkpoint
IBM Power Systems
1. True or False: A logical volume can span more than one physical
volume.
2. True or False: A logical volume can span more than one 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: Striping can be combined with mirroring to provide

increased performance and availability.

Checkpoint solutions
IBM Power Systems
1. True or False: A logical volume can span more than one physical
volume.
The answer is true.
2. True or False: A logical volume can span more than one volume
group.
The answer is false.
3. True or False: The contents of a physical volume can be divided
between two volume groups.
The answer is false.
4. True or False: If mirroring logical volumes, it is not necessary to
perform a backup.
The answer is false. You still need to back up to external media.
5. True or False: Striping can be combined with mirroring to provide
increased performance and availability
The answer is true.
Exercise
IBM Power Systems
Working with LVM

Unit summary
IBM Power Systems
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


Working With The Logical Volume Manager

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Working With The Logical Volume Manager

Enviado por

Direitos autorais:

Formatos disponíveis

Working with the Logical Volume

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

After completing this unit, you should be able to:

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

# smit mkvg mkvg –y datavg hdisk1 hdisk2

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

# smit mkvg mkvg –S –y db2_vg hdisk3

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

# smit chvg chvg –a n –Q n datavg

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

# smit reducevg2 reducevg -df db2_vg hdisk2 hdisk3

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

# smit varyonvg varyonvg datavg

# smit varyoffvg varyoffvg datavg

# smit importvg importvg –y datavg hdisk3

# smit exportvg exportvg datavg

Note: The volume group must be inactive before it is exported.

Logical Volume Manager

• LVM supports the following three software RAID configurations:

• Striping aides performance, whereas mirroring aides availability.

• In today’s environment, most data resides in SANs. Disks in a SAN are

• Inter- and intra-policy

• Mirror write consistency

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

• Mirroring is when a logical partition maps to more than one

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

• When mirroring, it is essential that all PP copies are stored on

• This setting is controlled by the Allocation policy.

• Allocation can be set to:

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

• Consecutive stripe units are

• Meets performance and high availability requirements

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

• Mirror pools simplify the task of isolating a logical volume

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

• Intra-physical volume allocation policy

• Inter-physical volume allocation policy

• Scheduling policies when mirroring:

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

• Problem: If the system crashes before the write to all mirrors

• Solution: Mirror write consistency

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

• Show LP to PP relationship on disks

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

• reorgvg moves physical partition allocations for logical

• # chlv –e x mylv (set to maximum number of disks)

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

# smit mklvcopy mklvcopy -k datalv 3 hdisk4

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

# smit extendlv extendlv datalv 20

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

# smit rmlv rmlv –f datalv2

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

• Mirroring rootvg is very important.

PV1 Volume group PV2

© Copyright IBM Corporation 2009, 2013. All Rights Reserved.

• List all physical volumes in the system.