Veritas Storage Foundation and High Availability Solutions Release Notes
Veritas Storage Foundation⢠and High ... - SORT - Symantec Veritas Storage Foundation⢠and High ... - SORT - Symantec
32About Veritas Storage Foundation and High Availability SolutionsFixed issuesTable 1-7Fixedissues290782328991732898547289298328864022886333287887628759622869594286699728660592859470285885328514032851085Veritas Volume Manager 6.0.3 fixed issues (continued)DescriptionIf the user removes the lun at the storage layer and at VxVM layerbeforehand, DMP DR tool is unable to clean-up cfgadm (leadville) stack.vxconfigd hang after executing the vradmin stoprep comand.vradmind on VVR Secondary Site dumps core, when Logowner Service Groupon VVR (Veritas Volume Replicator) Primary Site is shuffled across its CVM(Clustered Volume Manager) nodes.vxvol dumps core if new links are added while the operation is in progress.vxconfigd hang while executing tc ./scripts/ddl/dmpapm.tc#11The vxdg(1M) join command should not allow mixing clone and non-clonedisks in a DiskGroup.vxconfigd dumps core in vol_cbr_dolog() due to race between two threadsprocessing requests from the same client.During the upgrade of VRTSaslapm package, a conflict is encountered withVRTSvxvm package because an APM binary is included in VRTSvxvmpackage which is already installedMaster node panics due to corruption if space optimized snapshots arerefreshed and 'vxclustadm setmaster' is used to select master.Initializing using vxdisksetup -i and Solaris patch 147440-20 gives errorVxVM vxdisksetup ERROR V-5-2-43 : Invalid disk device for vxdisksetupImproving error messages hit during the vxdisk resize operation.SRDF R2 with EFI label is not recognized by VxVM and showing in errorstatevxconfigd coredumps in dbf_fmt_tbl on the slave node after a Master Switchif you try to remove a disk from the DGThe vxportal and vxfs processes are failed to stop during first phase ofrolling upgrade.DMP doesn't detect implicit LUN ownership changes for some of thedmpnodes2837717The vxdisk(1M) resize command fails ifda name is specified.2836798Prevent DLE on simple/sliced disk with EFI label
About Veritas Storage Foundation and High Availability SolutionsFixed issues33Table 1-7Fixedissues28365282834046283349828261252815517280715828019622798673277958027539542744004274270627151292692012261960025676182510928Veritas Volume Manager 6.0.3 fixed issues (continued)Descriptionvxdisk resize is failing with error: "resize failed: New geometry makespartition unaligned"NFS migration failed due to device reminoring.vxconfigd hangs while reclaim operation is in progress on volumes havinginstant snapshotsVxVM script daemon is terminated abnormally when it is invoking withexact the same process id of the last invocation.vxdg adddisk should not allow mixing clone & non-clone disks in a DiskGroupOn Solaris platform, sometimes system can hang during VM upgrade orpatch installation.Grow of a volume takes significantly large time when the volume has version20 DCO (Data Change Object) attached to itSystem panics in voldco_alloc_layout() while creating volume with instantDCOSecondary node gives configuration error (no Primary RVG) after reboot ofmaster node on Primary site.At cable disconnect on port1 of dual-port FC HBA, paths via port2 are alsomarked SUSPECTvxconfigd is hung on the VVR secondary node during VVR configuration.Panic due to mutex not being released in vxlo_openvxconfigd hangs during Master takeover in a CVM (Clustered VolumeManager) environment.The vxevac move error message needs to be enhanced to be less generic andgive clear message for failure.Live migration of virtual machine having SFHA/SFCFSHA stack with datadisks fencing enabled, causes service groups configured on virtual machineto fault.VRTSexplorer coredumps in vxcheckhbaapi/print_target_map_entryExtended attributes for SRDF luns reported as Mirror with EMC (VMAXarray)
- Page 1 and 2: Veritas Storage Foundationand High
- Page 3 and 4: Symantec Corporation350 Ellis Stree
- Page 5 and 6: ■■■■■■■Hardware infor
- Page 7 and 8: ContentsTechnical Support .........
- Page 9 and 10: Contents9Chapter 4 Upgrading to 6.0
- Page 11 and 12: Chapter1About Veritas StorageFounda
- Page 13 and 14: About Veritas Storage Foundation an
- Page 15 and 16: About Veritas Storage Foundation an
- Page 17 and 18: About Veritas Storage Foundation an
- Page 19 and 20: About Veritas Storage Foundation an
- Page 21 and 22: About Veritas Storage Foundation an
- Page 23 and 24: About Veritas Storage Foundation an
- Page 25 and 26: About Veritas Storage Foundation an
- Page 27 and 28: About Veritas Storage Foundation an
- Page 29 and 30: About Veritas Storage Foundation an
- Page 31: About Veritas Storage Foundation an
- Page 35 and 36: About Veritas Storage Foundation an
- Page 37 and 38: About Veritas Storage Foundation an
- Page 39 and 40: About Veritas Storage Foundation an
- Page 41 and 42: About Veritas Storage Foundation an
- Page 43 and 44: About Veritas Storage Foundation an
- Page 45 and 46: About Veritas Storage Foundation an
- Page 47 and 48: About Veritas Storage Foundation an
- Page 49 and 50: About Veritas Storage Foundation an
- Page 51 and 52: About Veritas Storage Foundation an
- Page 53 and 54: About Veritas Storage Foundation an
- Page 55 and 56: About Veritas Storage Foundation an
- Page 57 and 58: About Veritas Storage Foundation an
- Page 59 and 60: About Veritas Storage Foundation an
- Page 61 and 62: About Veritas Storage Foundation an
- Page 63 and 64: About Veritas Storage Foundation an
- Page 65 and 66: About Veritas Storage Foundation an
- Page 67 and 68: About Veritas Storage Foundation an
- Page 69 and 70: About Veritas Storage Foundation an
- Page 71 and 72: About Veritas Storage Foundation an
- Page 73 and 74: About Veritas Storage Foundation an
- Page 75 and 76: About Veritas Storage Foundation an
- Page 77 and 78: About Veritas Storage Foundation an
- Page 79 and 80: About Veritas Storage Foundation an
- Page 81 and 82: About Veritas Storage Foundation an
32About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Fixed issuesTable 1-7Fixedissues290782328991732898547289298328864022886333287887628759622869594286699728660592859470285885328514032851085<strong>Veritas</strong> Volume Manager 6.0.3 fixed issues (continued)DescriptionIf the user removes the lun at the storage layer <strong>and</strong> at VxVM layerbeforeh<strong>and</strong>, DMP DR tool is unable to clean-up cfgadm (leadville) stack.vxconfigd hang after executing the vradmin stoprep com<strong>and</strong>.vradmind on VVR Secondary Site dumps core, when Logowner Service Groupon VVR (<strong>Veritas</strong> Volume Replicator) Primary Site is shuffled across its CVM(Clustered Volume Manager) nodes.vxvol dumps core if new links are added while the operation is in progress.vxconfigd hang while executing tc ./scripts/ddl/dmpapm.tc#11The vxdg(1M) join comm<strong>and</strong> should not allow mixing clone <strong>and</strong> non-clonedisks in a DiskGroup.vxconfigd dumps core in vol_cbr_dolog() due to race between two threadsprocessing requests from the same client.During the upgrade of VRTSaslapm package, a conflict is encountered withVRTSvxvm package because an APM binary is included in VRTSvxvmpackage which is already installedMaster node panics due to corruption if space optimized snapshots arerefreshed <strong>and</strong> 'vxclustadm setmaster' is used to select master.Initializing using vxdisksetup -i <strong>and</strong> Solaris patch 147440-20 gives errorVxVM vxdisksetup ERROR V-5-2-43 : Invalid disk device for vxdisksetupImproving error messages hit during the vxdisk resize operation.SRDF R2 with EFI label is not recognized by VxVM <strong>and</strong> showing in errorstatevxconfigd coredumps in dbf_fmt_tbl on the slave node after a Master Switchif you try to remove a disk from the DGThe vxportal <strong>and</strong> vxfs processes are failed to stop during first phase ofrolling upgrade.DMP doesn't detect implicit LUN ownership changes for some of thedmpnodes2837717The vxdisk(1M) resize comm<strong>and</strong> fails ifda name is specified.2836798Prevent DLE on simple/sliced disk with EFI label
Change language