Veritas Storage Foundation and High Availability Solutions Release Notes
Veritas Storage Foundation⢠and High ... - SORT - Symantec
Veritas Storage Foundation⢠and High ... - SORT - Symantec
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
62About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Known issuesunless the number of cylinders go beyond 2^16-1 (65535) . Because of the VTOClimitation of storing geometry values only till 2^16 -1, if the number of cylindersincreases beyond the limit, vxdisk resize increases the cylinder size. If thishappens, the private region will overlap with the public region data <strong>and</strong> corruptthe user data.As a result of this LUN geometry change, VxVM is unable to complete vxdiskresize on simple format disks. VxVM was not designed to h<strong>and</strong>le such geometrychanges during Dynamic LUN Expansion operations on simple disks.Workaround:The VxVM vxdisk resize comm<strong>and</strong> behaves differently depending on whetherthe disk is simple, sliced, or CDS format.The problem shown above only occurs on simple disk configurations. As a resultof this difference in behavior, if the geometry changes during a Dynamic LUNExpansion operation at the LUN level, you can convert the disk to a CDS formatdisk. Use the vxcdsconvert comm<strong>and</strong> on the disk. Then you can issue the vxdiskresize comm<strong>and</strong>.See http://www.symantec.com/docs/TECH136240 for more information.Exp<strong>and</strong>ing a LUN to a size greater than 1 TB fails to show correct exp<strong>and</strong>edsize (2123677)This issue occurs when you perform a Dynamic LUN Expansion for a LUN that issmaller than 1 TB <strong>and</strong> increase the size to greater than 1 Tb. After the expansion,<strong>Veritas</strong> Volume Manager (VxVM) fails ongoing I/O, <strong>and</strong> the public region size isreset to original size. After you run the vxdisk sc<strong>and</strong>isks comm<strong>and</strong>, VxVM doesnot show the correct exp<strong>and</strong>ed size of the LUN. The issue is due to underlyingSolaris issues. Refer to Sun Bug Id 6929449 <strong>and</strong> Sun Bug Id 6912703.Workaround:There is no workaround.1 TB luns goes in error state with Solaris x86 (2706776)If you label a disk device as EFI using format on a subset of the paths or on theDMP device, Solaris will not be able to propagate the label to all the other pathsof the LUN. This will lead the device to appear in the error state under 'vxdisklist'.Workaround:There is no workaround for this issue.
Change language