Veritas Storage Foundation and High Availability Solutions Release Notes

More documents

Recommendations

Info

56About Veritas Storage Foundation and High Availability SolutionsKnown issuesfffffe8000988ab0 genunix:mdi_pi_online+32 ()fffffe8000988b20 fcp:ssfcp_online_child+ff ()fffffe8000988b90 fcp:ssfcp_trigger_lun+2b0 ()fffffe8000988bc0 fcp:ssfcp_hp_task+88 ()fffffe8000988c40 genunix:taskq_thread+295 ()fffffe8000988c50 unix:thread_start+8 ()For more information, see Oracle bug ID 7079724.Workaround:Disable Solaris I/O multi-pathing on the server to avoid the system panic.To disable Solaris I/O multi-pathing on the server1 Disable Solaris I/O multi-pathing:# stmsboot -d2 Reboot the server:# rebootVeritas Volume Manager known issuesThe following are the Veritas Volume Manager known issues for this release.Dynamic LUN expansion is not supported for EFI disks in simple or slicedformats (2836798)Dynamic LUN expansion is not supported for EFI (Extensible Firmware Interface)disks in simple or sliced formats. It may lead to corruption. The recommendedformat is the Cross-platform Data Sharing (CDS) disk format.Workaround:Convert the disk format to CDS using the vxcdsconvert utility.The vxrecover command does not handle RAID5 volumes correctly (2715124)The vxrecover command calls the recovery process for the top-level volume,which internally takes care of recovering its subvolumes. The vxrecover commanddoes not handle RAID5 volumes correctly. The recovery process fails to recoverthe subvolumes, which remain in the NEEDSYNC state.Workaround:Manually recover the RAID5 volumes using the vxvol utility, as follows:# vxvol -g diskgroup resync volume
About Veritas Storage Foundation and High Availability SolutionsKnown issues57The vxcdsconvert utility is supported only on the master node (2616422)The vxcdsconvert utility should be run only from the master node, not from theslave nodes of the cluster.Veritas Volume Manager (VxVM) might report false serial split brain undercertain scenarios (1834513)VxVM might detect and report a false serial split brain when all of the followingconditions are met:■■One or more arrays that provide the shared storage for the cluster are beingpowered offAt the same time when the arrays are being powered off, an operation thatrequires an internal transaction is initiated (such as VxVM configurationcommands)In such a scenario, disk group import will fail with a split brain error and thevxsplitlines output will show 0 or 1 pools.Workaround:To recover from this situation1 Retrieve the disk media identifier (dm_id) from the configuration copy:# /etc/vx/diag.d/vxprivutil dumpconfig device-pathThe dm_id is also the serial split brain id (ssbid)2 Use the dm_id in the following command to recover from the situation:# /etc/vx/diag.d/vxprivutil set device-path ssbid=dm_idThe relayout operation fails when there are too many disks in the diskgroup. (2015135)The attempted relayout operation on a disk group containing approximately morethan 300 LUNs or disks may fail with the following error:Cannot setup spaceExpanding a LUN to a size greater than 1 TB fails to show correct expandedsize (2123677)This issue occurs when you perform a Dynamic LUN Expansion for a LUN that issmaller than 1 TB and increase the size to greater than 1 Tb. After the expansion,Veritas Volume Manager (VxVM) fails ongoing I/O, and the public region size isreset to original size. After you run the vxdisk scandisks command, VxVM does
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 55: About Veritas Storage Foundation an
Page 107 and 108:
About Veritas Storage Foundation an
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Chapter2Installing the products for
Page 151 and 152:
Installing the products for the fir
Page 153 and 154:
Installing the products for the fir
Page 155 and 156:
Chapter3Installing the productsusin
Page 157 and 158:
Installing the products using JumpS
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Chapter4Upgrading to 6.0.3This chap
Page 165 and 166:
Upgrading to 6.0.3Upgrading to 6.0.
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Upgrading to 6.0.3Verifying softwar
Page 195 and 196:
Chapter5Uninstalling version 6.0.3T
Page 197 and 198:
Uninstalling version 6.0.3Rolling b
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
AppendixAConfiguring VCS to managea
Page 223 and 224:
Configuring VCS to manage a Logical
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
show all

Veritas Storage Foundation and High Availability Solutions Release Notes

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?