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>Known issues47Lack of install script to configure product after installingsfcfsha6.0.1 (2978290)For Solaris11 U1, there are no install scripts in the /opt/VRTS/install directoryto configure the SF product.Workaround:On Solaris 11 U1, install 6.0.1, upgrade to 6.0.3 <strong>and</strong> then configure the productusing the newly generated install scripts under /opt/VRTS/install.The svc:/system/VRTSperl-runonce:default SMF service in themaintenance state (3089938)After upgrade from 6.0.1 to 6.0.3 on Solaris 11 SPARC, the svc:/system/VRTSperlrunonce:defaultSMF service may be in the maintenance state.Workaround:If you find the svc:/system/VRTSperl-runonce:default SMF service in themaintenance state, perform the following steps:1. # svcadm disable svc:/system/VRTSperl-runonce:default2. # svccfg delete -f svc:/system/VRTSperl-runonce:defaultAlso you can ignore the following message from the console:svc.startd[11]: svc:/system/VRTSperl-runonce:default: Method"/opt/VRTSperl/bin/runonce" failed with exit status 127<strong>Veritas</strong> Dynamic Multi-pathing known issuesThis section describes the <strong>Veritas</strong> Dynamic Multi-pathing known issues in 6.0.3<strong>and</strong> 6.0.1.Creating a zpool fails with a incorrect disk size error (2277875)When the tunable parameter dmp_native_support is turned on, creating a zpoolon DMP devices may fail with the following error:one or more devices is less than the minimum size (64 M)This error may occur even if the device size is greater than the required minimumsize.Workaround:To resolve this issue, use one of the following comm<strong>and</strong>s:

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

Saved successfully!

Ooh no, something went wrong!