Veritas Storage Foundation and High Availability Solutions Release Notes
Veritas Storage Foundation⢠and High ... - SORT - Symantec Veritas Storage Foundation⢠and High ... - SORT - Symantec
68About Veritas Storage Foundation and High Availability SolutionsKnown issuesSevere impact in read performance (sequential and random) on compressedfiles compared to uncompressed files (2609152)The read throughput is highly degraded for compressed files. The difference isseen for sequential I/O and random I/O. For sequential reads, the degrdataion isvisbile even when the amount of data read compressed files is one-third of theuncompressed files (compression ratio).Workaround:There is no workaround for this issue.fsppadm operations issued on multi-volume file system fail if there areother mounted file systems with a disk layout Version less than 6 (2909206)The fsppadm command checks all mounted file systems, and if it finds any filesystems with a disk layout Version that is less than 6, then it exits with thefollowing error message:# fsppadm assign /dst_vset /tmp/pol_test.xmlUX:vxfs fsppadm: ERROR: V-3-26510: Low level Volume enumeration failureon / with messageFunction not implementedThis error occurs because the fsppadm command functionality is not supportedon a disk layout Version that is less than 6.Workaround:There is no workaround for this issue.Internal tests hit assert "f:vx_putpage1:1a" on Solaris11 U1 SRU2.5(3060829)The assert failure will not cause any outage but may lead to performance issueson systems with large memory and swap file configurations. This is due to a knowndefect on Solaris 11 update 1, refer to the Bug ID below for more details on theOracle support site:Bug ID: 15813035SUNBT7194962 pageout no longer pushes pages asynchronously.Workaround:There is no workaround for this issue.Replication known issuesThis section describes the replication known issues in this release of VeritasStorage Foundation.
About Veritas Storage Foundation and High Availability SolutionsKnown issues69vradmin syncvol command compatibility with IPv6 addresses (2075307)The vradmin syncvol command does not work with the compressed form of IPv6addresses if the target disk group and volume names are not specified.Workaround:In IPv6 environments, if you run the vradmin syncvol command and identifythe target host using the compressed form of the IPv6 address, then you also needto specify the target disk group and volume names.RVGPrimary agent operation to start replication between the originalPrimary and the bunker fails during failback (2054804)The RVGPrimary agent initiated operation to start replication between the originalPrimary and the bunker fails during failback – when migrating back to the originalPrimary after disaster recovery – with the error message:VxVM VVR vxrlink ERROR V-5-1-5282 Error getting information fromremote host. Internal Error.The issue applies to global clustering with a bunker configuration, where thebunker replication is configured using storage protocol. It occurs when the Primarycomes back even before the bunker disk group is imported on the bunker host toinitialize the bunker replay by the RVGPrimary agent in the Secondary cluster.Workaround:To resolve this issue1 Before failback, make sure that bunker replay is either completed or aborted.2 After failback, deport and import the bunker disk group on the originalPrimary.3 Try the start replication operation from outside of VCS control.Bunker replay did not occur when the Application Service Group wasconfigured on some of the systems in the Primary cluster, andClusterFailoverPolicy is set to "AUTO" (2047724)The time that it takes for a global cluster to fail over an application service groupcan sometimes be smaller than the time that it takes for VVR to detect theconfiguration change associated with the primary fault. This can occur in abunkered, globally clustered configuration when the value of theClusterFailoverPolicy attribute is Auto and the AppGroup is configured on asubset of nodes of the primary cluster.This causes the RVGPrimary online at the failover site to fail. The followingmessages appear in the VCS engine log:
- 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 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: 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
- Page 101 and 102: About Veritas Storage Foundation an
- Page 103 and 104: About Veritas Storage Foundation an
- Page 105 and 106: About Veritas Storage Foundation an
- Page 107 and 108: About Veritas Storage Foundation an
- Page 109 and 110: About Veritas Storage Foundation an
- Page 111 and 112: About Veritas Storage Foundation an
- Page 113 and 114: About Veritas Storage Foundation an
- Page 115 and 116: About Veritas Storage Foundation an
- Page 117 and 118: About Veritas Storage Foundation an
68About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Known issuesSevere impact in read performance (sequential <strong>and</strong> r<strong>and</strong>om) on compressedfiles compared to uncompressed files (2609152)The read throughput is highly degraded for compressed files. The difference isseen for sequential I/O <strong>and</strong> r<strong>and</strong>om I/O. For sequential reads, the degrdataion isvisbile even when the amount of data read compressed files is one-third of theuncompressed files (compression ratio).Workaround:There is no workaround for this issue.fsppadm operations issued on multi-volume file system fail if there areother mounted file systems with a disk layout Version less than 6 (2909206)The fsppadm comm<strong>and</strong> checks all mounted file systems, <strong>and</strong> if it finds any filesystems with a disk layout Version that is less than 6, then it exits with thefollowing error message:# fsppadm assign /dst_vset /tmp/pol_test.xmlUX:vxfs fsppadm: ERROR: V-3-26510: Low level Volume enumeration failureon / with messageFunction not implementedThis error occurs because the fsppadm comm<strong>and</strong> functionality is not supportedon a disk layout Version that is less than 6.Workaround:There is no workaround for this issue.Internal tests hit assert "f:vx_putpage1:1a" on Solaris11 U1 SRU2.5(3060829)The assert failure will not cause any outage but may lead to performance issueson systems with large memory <strong>and</strong> swap file configurations. This is due to a knowndefect on Solaris 11 update 1, refer to the Bug ID below for more details on theOracle support site:Bug ID: 15813035SUNBT7194962 pageout no longer pushes pages asynchronously.Workaround:There is no workaround for this issue.Replication known issuesThis section describes the replication known issues in this release of <strong>Veritas</strong><strong>Storage</strong> <strong>Foundation</strong>.