README VERSION : 1.1 README CREATION DATE : 2014-04-07 PATCH-ID : 6.0.500.000 PATCH NAME : VRTSlvmconv 6.0.500.000 BASE PACKAGE NAME : VRTSlvmconv BASE PACKAGE VERSION : 6.0.100.000 SUPERSEDED PATCHES : NONE REQUIRED PATCHES : NONE INCOMPATIBLE PATCHES : NONE SUPPORTED PADV : sles11_x86_64 (P-PLATFORM , A-ARCHITECTURE , D-DISTRIBUTION , V-VERSION) PATCH CATEGORY : OTHER PATCH CRITICALITY : OPTIONAL HAS KERNEL COMPONENT : NO ID : NONE REBOOT REQUIRED : NO REQUIRE APPLICATION DOWNTIME : NO PATCH INSTALLATION INSTRUCTIONS: -------------------------------- Please refer to Install guide for install instructions PATCH UNINSTALLATION INSTRUCTIONS: ---------------------------------- Please refer to Install guide for uninstall instructions SPECIAL INSTALL INSTRUCTIONS: ----------------------------- NONE SUMMARY OF FIXED ISSUES: ----------------------------------------- PATCH ID:6.0.500.000 3344264 (3220929) The Veritas Volume Manager (VxVM) fails to convert a logical volume manager (LVM) volume to Veritas Volume Manager (VxVM) volume. 3350979 (3261485) The vxcdsconvert(1M) utility failed with the error "Unable to initialize the disk as a CDS disk". 3394692 (3421236) The vxautoconvert/vxvmconvert utility command fails to convert LVM (Logical Volume Manager) to VxVM (Veritas Volume Manager) causing data loss. 3395095 (3416098) The vxvmconvert utility throws error during execution. 3429328 (3433931) The AvxvmconvertA utility fails to get the correct LVM version. SUMMARY OF KNOWN ISSUES: ----------------------------------------- 2892689(2836798) Dynamic LUN expansion is not supported for EFI disks in simple or sliced formats KNOWN ISSUES : -------------- * INCIDENT NO::2892689 TRACKING ID ::2836798 SYMPTOM:: Dynamic LUN expansion is not supported for EFI (Extensible Firmware Interface) disks in simple or sliced formats. The recommended format is the Cross-platform Data Sharing (CDS) disk format. WORKAROUND:: Convert the disk format to CDS using the vxcdsconvert utility. FIXED INCIDENTS: ---------------- PATCH ID:6.0.500.000 * INCIDENT NO:3344264 TRACKING ID:3220929 SYMPTOM: The vxvmconvert menu fails to convert logical volume manager (LVM) volume to Veritas Volume Manager (VxVM) volume. DESCRIPTION: With the latest RHEL release, the LVM lvdisplay(1M) command has a new output format. In the previous RHEL release, the lvdisplay(1M) command output contained the LV Name field. This field provided the absolute path of the LVM volume. However, in the latest RHEL release, the LV Name field contains the base name and a new LV Path field provides the absolute path. The vxvmconvert menu does not recognize the field change in the LVM's lvdisplay(1M) command output and fails to convert the LVM volumes to VVM volumes. RESOLUTION: The code is modified to enable VxVM to recognize the lvdisplay(1M)command's new output format. * INCIDENT NO:3350979 TRACKING ID:3261485 SYMPTOM: The vxcdsconvert(1M) utility fails with following error messages: VxVM vxcdsconvert ERROR V-5-2-2777 : Unable to initialize the disk as a CDS disk VxVM vxcdsconvert ERROR V-5-2-2780 : Unable to move volume off of the disk VxVM vxcdsconvert ERROR V-5-2-3120 Conversion process aborted DESCRIPTION: As part of the conversion process, the vxcdsconvert(1M) utility moves all the volumes to some other disk, before the disk is initialized with the CDS format. On the VxVM formatted disks apart from the CDS format, the VxVM volume starts immediately in the PUBLIC partition. If LVM or FS was stamped on the disk, even after the data migration to some other disk within the disk group, this signature is not erased. As part of the vxcdsconvert operation, when the disk is destroyed, only the SLICED tags are erased but the partition table still exists. The disk is then recognized to have a file system or LVM on the partition where the PUBLIC region existed earlier. The vxcdsconvert(1M) utility fails because the vxdisksetup which is invoked internally to initialize the disk with the CDS format, prevents the disk initialization for any foreign FS or LVM. RESOLUTION: The code is modified so that the vxcdsconvert(1M) utility forcefully invokes the vxdisksetup(1M) command to erase any foreign format. * INCIDENT NO:3394692 TRACKING ID:3421236 SYMPTOM: The vxautoconvert/vxvmconvert utility command fails to convert LVM (Logical Volume Manager) to VxVM (Veritas Volume Manager) causing data loss. DESCRIPTION: The following issues were observed with vxautoconvert and vxvmconvert tools: 1) Disk's partition table used is not in sync with the kernel copy of partition table on disk. This is because after running the pvcreate command, it writes LVM stamp but destroys the partition table on disk. Therefore, the LVM used is referred to as stale entry. 2) Vxautoconvert does not export current LVM version, hence, during further operation, the comparison of the LVM version fails. 3) LVM command "pvmove" fails with multi-pathed disk. 4) If the conversion is cancelled, then the stopped LVM volumes are not reverted back to active state. RESOLUTION: The code is modified to ensure that the disk partition table is in sync, to hide extra path during the pvmove operation so that the operation is successful. The code is also modified such that the vxautoconvert exports current LVM version and if, the conversion is cancelled, then the stopped LVM volumes are restored to active state. * INCIDENT NO:3395095 TRACKING ID:3416098 SYMPTOM: "vxvmconvert" utility throws error during execution. The following error message is displayed. "[: 100-RHEL6: integer expression expected". DESCRIPTION: In vxvmconvert utility, the sed (stream editor) expression which is used to parse and extract the Logical Volume Manager (LVM) version is not appropriate and fails for particular RHEL(Red Hat Enterprise Linux) version. RESOLUTION: Code changes are done so that the expression parses correctly. * INCIDENT NO:3429328 TRACKING ID:3433931 SYMPTOM: The AvxvmconvertAutility fails to get the correct Logical Volume Manager (LVM) version and reports following message: "vxvmconvert is not supported if LVM version is lower than 2.02.61 and Disk having multiple path" DESCRIPTION: In the AvxvmconvertA utility, an incorrect stream editor (sed) expression is used to parse and extract the LVM version. Due to which the expression failed for build versions greater than two digits. RESOLUTION: The code is modified to parse the expression correctly. INCIDENTS FROM OLD PATCHES: --------------------------- NONE