Veritas Storage Foundation and High Availability Solutions Release Notes

More documents

Recommendations

Info

58About Veritas Storage Foundation and High Availability SolutionsKnown issuesnot show the correct expanded size of the LUN. The issue is due to underlyingSolaris issues. Refer to Sun Bug Id 6929449 and Sun Bug Id 6912703.Workaround:There is no workaround for this issue.Co-existence check might fail for CDS disks (2214952)In Veritas Volume Manager (VxVM) 5.1 SP1, VxVM introduces the ability to supportCross-platform Data Sharing (CDS) on disks larger than 1 TB. VxVM uses the SUNVTOC Table to initialize the cdsdisk layout on devices up to 1 TB. VxVM uses theGUID Partition Table (GPT) to initialize the cdsdisk layout on devices larger than1 TB.In layouts where SUN VTOC Table is used for initialization (typically, when thedisk size has never exceeded 1 TB), the AIX co-existence label can be found atsector 7 and VxVM ID block (also known as HP co-existence label) can be foundat sector 16.In layouts where GPT is used for initialization (typically, when the disk size iscurrently greater than or had earlier exceeded 1 TB), the AIX co-existence labelis placed at sector 55 and VxVM ID block (also known as HP co-existence label) isplaced at sector 64. Consequently, AIX utilities would not be able to recognize acdsdisk initialized using GPT to be a valid VxVM disk. Symantec is working withIBM and third party OEMs to enhance the co-existence check in these utilities.Workaround:There is no workaround for this issue.Probing vxio with DTrace fails on SPARC machines. (2180635)This issue exists because of inability of DTrace to load a module whose text sizeis greater than 2MB on SPARC machines. While trying to load vxio with DTraceyou may see following warning messages on console:dtrace: WARNING: couldn't allocate SDT table for module vxiofbt: WARNING: couldn't allocate FBT table for module vxioWorkaround:There is no workaround for this issue.The "vxdg listclone" command output may not list all the disks with"clone_disk" or "udid_mismatch" flag set (2354560)In Cluster Volume Manager environment, "vxdg listclone" command output maynot list all the disks with "clone_disk" or "udid_mismatch" flag set. This can happenon master/slave nodes.
About Veritas Storage Foundation and High Availability SolutionsKnown issues59Workaround:Administrator has to run "vxdisk scandisks" or "vxdisk -o alldgs list" followed by"vxdg listclone" to get all the disks containing "clone_disk" or "udid_mismatch"flag on respective host.The vxsnap print command shows incorrect value for percentage dirty(2360780)The vxsnap print command can display the percentage of regions that differbetween snapshots, shown as the %dirty. In SF 6.0, if this command is run whilethe volumes are online and being actively used, the shown %dirty may lag fromactual percentage dirty for instant snap data cache object (DCO) volumes. Thatis, the command output may show less %dirty than actual.Issues with the disk state on the CVM slave node when vxconfigd isrestarted on all nodes (2615680)When a CVM master node and a slave node have lost storage access, and vxconfigdis restarted on all nodes, the disk state on the CVM slave node shows as invalid.Workaround:To work around this issue1 Restore storage connectivity.2 Deport the disk group.3 Import the disk group.Removing an array node from an IBM Storwize V7000 storage system alsoremoves the controller (2816589)When using an IBM Storwize V7000 storage system, after removing one arraynode, the corresponding controller is also removed.Workaround: The following procedure resolves this issue.To resolve this issue1 Set the iotimeout tunable to 600:# vxdmpadm setattr enclosure encl1 recoveryoption=throttle \iotimeout=6002 After you re-add the SAN VC node, run the vxdctl enable command forDynamic Multi-Pathing (DMP) to detect the added paths:# vxdctl enable
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 57: About Veritas Storage Foundation an
Page 109 and 110:
About Veritas Storage Foundation an
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

Create successful ePaper yourself

Delete template?

Save as template?