Veritas Storage Foundation and High Availability Solutions Release Notes
Veritas Storage Foundation⢠and High ... - SORT - Symantec Veritas Storage Foundation⢠and High ... - SORT - Symantec
50About Veritas Storage Foundation and High Availability SolutionsKnown issuesContinuous trespass loop when a CLARiiON LUN is mapped toa different host than its snapshot (2761567)If a CLARiiON LUN is mapped to a different host than its snapshot, a trespass onone of them could cause a trespass on the other. This behavior could result in aloop for these LUNs, as DMP tries to fail back the LUNs if the primary paths areavailable.Workaround:To avoid this issue, turn off the dmp_monitor_ownership tunable:# vxdmpadm settune dmp_monitor_ownership=offAfter excluding devices managed by PowerPath from VxVM,the devices still show as DMP devices (2494632)The issue happens after EMC PowerPath is installed and all devices are underPowerPath control. If you want to maintain the devices under PowerPath control,you use the following command to exclude the device that is managed byPowerPath from VxVM:# vxdmpadm exclude dmpnodename=PowerPath_device _nameAfter system reboot, the PowerPath device still shows as a DMP device, althoughthe device is managed by EMC PowerPath.Workaround:This issue is seen only during the first bootup discovery after reboot. To resolvethe issue, manually trigger DMP device discovery:# vxdisk scandisksThe system may hang with Solaris 11 SRU1 (2876211)When running Solaris 11 SRU1, the system may hang due to an Oracle bug. TheOracle Bug ID is 7105131 deadman panic.Workaround: SRU1 for Solaris 11 should be updated to SRU2a. The bug is fixedin SRU2a: Oracle Solaris 11 Support Repository Updates (SRU) Index (Doc ID1372094.1)System panics because dmp_signal_event() called psignal()with incorrect vxesd proc pointer (3041167)On Solaris 11 SPARC SRU1, system panics after executing the vxrecover operationon the master node.
About Veritas Storage Foundation and High Availability SolutionsKnown issues51Workaround:There is no workaround for this issue in 6.0.3.Veritas Storage Foundation known issuesThis section describes the Veritas Storage Foundation known issues in 6.0.3 and6.0.1.■■■■■Veritas Storage Foundation known issuesVeritas Volume Manager known issuesVeritas File System known issuesReplication known issuesVeritas Storage Foundation for Databases (SFDB) tools known issuesVeritas Storage Foundation known issuesThis section describes the known issues in this release of Veritas StorageFoundation (SF).Some dbed DST commands do not work correctly in non-POSIX locales(2138030)Some dbed DST commands do not work correctly in non-POSIX locale settings.Workaround:Set the environment variable LANG=C systemwide in the /etc/profile file.In an IPv6 environment, db2icrt and db2idrop commands return asegmentation fault error during instance creation and instance removal(1602444)When using IBM DB2 db2icrt command to create a DB2 database instance on apure IPv6 environment, the db2icrt command returns segmentation fault errormessage. For example:$ /opt/ibm/db2/V9.5/instance/db2icrt -a server -u db2fen1 db2inst1/opt/ibm/db2/V9.5/instance/db2iutil: line 4700: 26182 Segmentation fault$ {DB2DIR?}/instance/db2isrv -addfcm -i ${INSTNAME?}The db2idrop command also returns segmentation fault, but the instance isremoved successfully after the db2idrop command is issued. For example:$ /opt/ibm/db2/V9.5/instance/db2idrop db2inst1/opt/ibm/db2/V9.5/instance/db2iutil: line 3599:7350 Segmentation fault
- 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 and 32: About Veritas Storage Foundation an
- Page 33 and 34: 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: 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
- Page 83 and 84: About Veritas Storage Foundation an
- Page 85 and 86: About Veritas Storage Foundation an
- Page 87 and 88: About Veritas Storage Foundation an
- Page 89 and 90: About Veritas Storage Foundation an
- Page 91 and 92: About Veritas Storage Foundation an
- Page 93 and 94: About Veritas Storage Foundation an
- Page 95 and 96: About Veritas Storage Foundation an
- Page 97 and 98: About Veritas Storage Foundation an
- Page 99 and 100: About Veritas Storage Foundation an
50About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Known issuesContinuous trespass loop when a CLARiiON LUN is mapped toa different host than its snapshot (2761567)If a CLARiiON LUN is mapped to a different host than its snapshot, a trespass onone of them could cause a trespass on the other. This behavior could result in aloop for these LUNs, as DMP tries to fail back the LUNs if the primary paths areavailable.Workaround:To avoid this issue, turn off the dmp_monitor_ownership tunable:# vxdmpadm settune dmp_monitor_ownership=offAfter excluding devices managed by PowerPath from VxVM,the devices still show as DMP devices (2494632)The issue happens after EMC PowerPath is installed <strong>and</strong> all devices are underPowerPath control. If you want to maintain the devices under PowerPath control,you use the following comm<strong>and</strong> to exclude the device that is managed byPowerPath from VxVM:# vxdmpadm exclude dmpnodename=PowerPath_device _nameAfter system reboot, the PowerPath device still shows as a DMP device, althoughthe device is managed by EMC PowerPath.Workaround:This issue is seen only during the first bootup discovery after reboot. To resolvethe issue, manually trigger DMP device discovery:# vxdisk sc<strong>and</strong>isksThe system may hang with Solaris 11 SRU1 (2876211)When running Solaris 11 SRU1, the system may hang due to an Oracle bug. TheOracle Bug ID is 7105131 deadman panic.Workaround: SRU1 for Solaris 11 should be updated to SRU2a. The bug is fixedin SRU2a: Oracle Solaris 11 Support Repository Updates (SRU) Index (Doc ID1372094.1)System panics because dmp_signal_event() called psignal()with incorrect vxesd proc pointer (3041167)On Solaris 11 SPARC SRU1, system panics after executing the vxrecover operationon the master node.
Change language