17.08.2015 Views

Veritas Storage Foundation and High Availability Solutions Release Notes

Veritas Storage Foundation™ and High ... - SORT - Symantec

Veritas Storage Foundation™ and High ... - SORT - Symantec

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Software limitations131<strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> software limitationsThis section describes the <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> software limitations in6.0.3 <strong>and</strong> 6.0.1.<strong>Veritas</strong> Volume Manager software limitationsThe following are software limitations in this release of <strong>Veritas</strong> Volume Manager.Converting a multi-pathed diskWhen converting a multi-pathed disk that is smaller than 1 TB from a VTOC labelto an EFI label, you must issue the format -e comm<strong>and</strong> for each path. For example,if a node has two paths, c1t2d0s2 <strong>and</strong> c2tsd0s2, you must run the format -ecomm<strong>and</strong> on each of the two paths.The vxlist comm<strong>and</strong> cannot correctly display numbers greater than or equalto 1 EBThe vxlist comm<strong>and</strong> <strong>and</strong> all of the other comm<strong>and</strong>s that use the same libraryas the vxlist comm<strong>and</strong> cannot correctly display numbers greater than or equalto 1 EB.You are unable to specify units in the tunables fileThe CPI displays an error when you set the unit type, such as MB or GB, for tunableparameters in the tunables file that you specify with the -tunablesfile fileoption. To avoid the error, you must set the unit type manually.Snapshot configuration with volumes in shared disk groups <strong>and</strong> privatedisk groups is not supportedA snapshot configuration with volumes in the shared disk groups <strong>and</strong> private diskgroups is not a recommended configuration. In this release, this configuration isnot supported.<strong>Storage</strong> reclamation does not happen on volumes with break-off snapshot(2798523)In this release, storage reclamation on a volume is prevented when it has abreak-off type snapshot. If storage reclamation is allowed on such volumes, it canlead to the following undesired situation. Instant snapshot operations, includingvxsnap refresh <strong>and</strong> vxsnap restore operations, lead to full synchronization ofeither the snapshot or the primary volume depending on the operation.In this release, if the volume has a snapshot, the storage reclamation is silentlyprevented. The physical storage is not reduced. The reclaim comm<strong>and</strong> reports

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!