How to solve the problem from vxevac with "ERROR V-5-1-438" and "ERROR V-5-2-3537"

Article:TECH144673  |  Created: 2010-11-20  |  Updated: 2012-07-21  |  Article URL http://www.symantec.com/docs/TECH144673
Article Type
Technical Solution


Environment

Issue



The customer fell through to conduct vxevac command line during the migration from one LUN to another (mirrored snapshot)
#/usr/lib/vxvm/bin/vxevac -g   sym_dg   original_lun   target_lun


Error



EXACT  ERROR  MESSAGES
------------------------------------------------------------------------------------------------------------------------
VxVM vxassist ERROR V-5-1-438 Cannot allocate space to replace subdisks
VxVM vxevac ERROR V-5-2-3537 Aborting disk evacuation
------------------------------------------------------------------------------------------------------------------------


Environment



1. OS: SunOS symc_sol 5.9 Generic_122300-54 sun4u sparc SUNW,Sun-Fire-V490
2. Package Version: SF4.1MP2


Cause



Since there was the fail in the course of conducging "vxevac" command line, the status of disk group, sym_dg shows the following condition.
------------------------------------------------------------------------------------------------------------------------
dg sym_dg   default      default  13000    1123114002.25.symc_sol

dm original_lun              HDS9500V01_3     auto     2048     545162496 NOHOTUSE
dm target_lun                 Disk_6                      auto     2048     549348096 NOHOTUSE
dm sp_dsk190_lun1     Disk_9                      auto     2048     549348096 NOHOTUSE
dm wm_dsk310_lun4   HDS9500V0_4        auto     2048     545162496 NOHOTUSE

sd target_lun-11 -       target_lun 249567392 268435456 - Disk_6   ENA    <<< This should be the new one and holding the allocated space.
------------------------------------------------------------------------------------------------------------------------

As it appears above, the disk group, sym_dg contains the unallocated space caused by incomplete vxevac operation.

So therefore, until this amount of space get free or new space is assigned, the next command, vxevac will keep failing to proceed data migration between disks.


Solution



[ WORKAROUND ]

1. Checking the current free space of disk group, sym_dg
symc_sol# vxdg -g sym_dg free
DISK             DEVICE                     TAG                 OFFSET       LENGTH    FLAGS
original_lun HDS9500V01_3 HDS9500V01_3         0               41943616       n
original_lun HDS9500V01_3 HDS9500V01_3   41945328      207634672    n
original_lun HDS9500V01_3 HDS9500V01_3   543200832    1961664        n
target_lun            Disk_6                 Disk_6             518002848    31345248      n

sp_dsk190_lun1 Disk_9                 Disk_9             369125744    180222352    n
wm_dsk310_lun4 HDS9500V0_4  HDS9500V0_4         0            545162496   n


2. Removing the prepared SD(Sub Disk) which is not in use.
symc_sol# vxedit -rfg sym_dg rm target_lun-11
 

3. Checking out the current remailed capacity of SDs(Sub Disks)
symc_sol# vxprint -htg sym_dg | grep  original_lun
dm original_lun HDS9500V01_3 auto   2048     545162496 NOHOTUSE

sd original_lun-11 u07_oraback_ordtag-02 original_lun 249580000 268435456 0 HDS9500V01_3 ENA
sd original_lun-13 u07_oraback_ordtag_dcl-01 original_lun 522209760 18992 0 HDS9500V01_3 ENA
sd original_lun-15 u07_oraexp_ordtag-02 original_lun 522229312 20971520 0 HDS9500V01_3 ENA
sd original_lun-14 u07_oraexp_ordtag_dcl-01 original_lun 41943616 1712 0 HDS9500V01_3 ENA
sd original_lun-12 var_oradump_ordtag-02 original_lun 518015456 4194304 0 HDS9500V01_3 ENA
sd original_lun-16 var_oradump_ordtag_dcl-01 original_lun 522228752 560 0 HDS9500V01_3 ENA


4. The output of summing up whole length number, original_lun
( Actually this is in process of checking the left entire space in the source disk that is going to be coppied to the target disk, that's to say "remained amount to be coppied"
)
------------------
268435456
+ 18992
+ 20971520
+ 1712
+ 4194304
+ 560
------------------
The number of sum-up.
293622544 <<<<<<

5. Checking the current free space of disk group, sym_dg
symc_sol# vxdg -g sym_dg free

symc_sol# vxdg -g sym_dg free
DISK             DEVICE                     TAG                 OFFSET       LENGTH    FLAGS
original_lun HDS9500V01_3 HDS9500V01_3         0               41943616       n
original_lun HDS9500V01_3 HDS9500V01_3   41945328      207634672    n
original_lun HDS9500V01_3 HDS9500V01_3   543200832    1961664        n
target_lun            Disk_6                 Disk_6             249567392  299780704    n

sp_dsk190_lun1 Disk_9                 Disk_9             369125744    180222352    n
wm_dsk310_lun4 HDS9500V0_4  HDS9500V0_4         0            545162496   n


6. So now it probes that the remaining space in the target node is bigger than the amount of sum-up length in the source disk as a result of removing the prepared sub disk, target_lun-11

293622544     <    299780704
( Source Disk)      ( Target Disk )

7. As there is a sufficient space left in the target disk,then the following command line will solve the problem.
#/usr/lib/vxvm/bin/vxevac -g sym_dg original_lun target_lun





Article URL http://www.symantec.com/docs/TECH144673


Terms of use for this information are found in Legal Notices