Veritas Storage Foundation and High Availability Solutions Release Notes

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.