From: Paul. Vanchope (cuihh6@HOTMAIL.COM)
Date: Mon Jan 05 2004 - 02:52:50 EST
#lspv
hdisk0 000c15af362c8c6d rootvg
hdisk9 000c15af9ecbe569 None
hdisk2 000c15afa59ad992 usrvg
hdisk1 000c15af28f1eabd usrvg
#lsvg usrvg
VOLUME GROUP: usrvg VG IDENTIFIER: 000c15af5cc1c5f3
VG STATE: active PP SIZE: 8 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 4338 (34704
megabytes)
MAX LVs: 256 FREE PPs: 4316 (34528
megabytes)
LVs: 9 USED PPs: 22 (176 megabytes)
OPEN LVs: 4 QUORUM: 2
TOTAL PVs: 2 VG DESCRIPTORS: 3
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 2 AUTO ON: yes
MAX PPs per PV: 3048 MAX PVs: 10
I created an LV using SMIT :
Logical volume NAME [slv6]
* VOLUME GROUP name usrvg
* Number of LOGICAL PARTITIONS
[1]
POSITION on physical volume
middle
RANGE of physical volumes
minimum
MAXIMUM NUMBER of PHYSICAL VOLUMES
[1]
to use for allocation
Number of COPIES of each logical
1
partition
Mirror Write Consistency?
yes
Allocate each logical partition copy superstrict
on a separate PV
Then i make an copy for the slv6 using "smitty mklvcopy":
[Entry
Fields]
* LOGICAL VOLUME name slv6
* NEW TOTAL number of logical partition
2
copies
POSITION on physical volume
middle
RANGE of physical volumes
minimum
MAXIMUM NUMBER of PHYSICAL VOLUMES
[1]
to use for allocation
Allocate each logical partition copy
on a separate PV superstrict
Then the following error appeared :
0516-404 allocp: This system cannot fulfill the allocation request.
There are not enough free partitions or not enough physical volumes
to keep strictness and satisfy allocation requests. The command
should be retried with different allocation characteristics.
Later i tried to use another method to achieve the goal, that is "making a
copy for the LV while creating the LV":
#smitty mklv
Logical volume NAME [slv5]
* VOLUME GROUP name usrvg
* Number of LOGICAL PARTITIONS
[1]
POSITION on physical volume
middle
RANGE of physical volumes
minimum
MAXIMUM NUMBER of PHYSICAL VOLUMES
[1]
to use for allocation
Number of COPIES of each logical
2
partition
Mirror Write Consistency?
yes
Allocate each logical partition copy superstrict
on a separate PV
Then it is successful to create the slv5 and make a copy for it .
#lslv -l slv5
slv5:N/A
PV COPIES IN BAND DISTRIBUTION
hdisk2 001:000:000 100% 000:001:000:000:000
hdisk1 001:000:000 100% 000:001:000:000:000
#lsvg -l usrvg
usrvg:
LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINT
testlv1 jfs 3 6 2 open/syncd /testlv1
testlv2 jfs 3 3 1 closed/syncd N/A
testlv3 jfs 3 3 1 closed/syncd N/A
loglv00 jfslog 1 1 1 open/syncd N/A
loglv01 jfslog 1 1 1 open/syncd N/A
testlv11 jfs 1 1 1 open/syncd /testlv11
slv5 jfs 1 2 2 closed/syncd N/A
I am confused with the above two methods for making an copy of LV. I think
they are the same in essence.
But Why the 1st method fail while the 2nd method can successfully finish
the mission ?
Anyone have such experiences ?
Thanks
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:17:26 EDT