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.
About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Known issues97SambaShare agent clean entry point fails when access to configuration fileon shared storage is lost [2858183]When the Samba server configuration file is on shared storage <strong>and</strong> access to theshared storage is lost, SambaShare agent clean entry point fails.Workaround: No workaround.SambaShare agent fails to offline resource in case of cable pull or onunplumbing of IP [2848020]When IP is unplumbed or in case of cable pull scenario, agent fails to offlineSambasShare resource.Workaround: No workaround.Entry points that run inside a zone are not cancelled cleanly [1179694]Cancelling entry points results in the cancellation of only the zlogin process. Thescript entry points that run inside a zone are forked off using the zlogin comm<strong>and</strong>.However, the zlogin comm<strong>and</strong> forks off an sh comm<strong>and</strong>, which runs in the contextof the Solaris zone. This shell process <strong>and</strong> its family do not inherit the group idof the zlogin process, <strong>and</strong> instead get a new group id. Thus, it is difficult for theagent framework to trace the children or gr<strong>and</strong>-children of the shell process,which translates to the cancellation of only the zlogin process.Workaround: Oracle must provide an API or a mechanism to kill all the childrenof the zlogin process that was started to run the entry point script in thelocal-zone.The zpool comm<strong>and</strong> runs into a loop if all storage paths from a node aredisabledThe Solaris Zpool agent runs zpool comm<strong>and</strong>s to import <strong>and</strong> export zpools. If allpaths to the storage are disabled, the zpool comm<strong>and</strong> does not respond. Instead,the zpool export comm<strong>and</strong> goes into a loop <strong>and</strong> attempts to export the zpool. Thiscontinues till the storage paths are restored <strong>and</strong> zpool is cleared. As a result, theoffline <strong>and</strong> clean procedures of Zpool Agent fail <strong>and</strong> the service group cannot failover to the other node.Workaround: You must restore the storage paths <strong>and</strong> run the zpool clear comm<strong>and</strong>for all the pending comm<strong>and</strong>s to succeed. This will cause the service group to failover to another node.Zone remains stuck in down state if tried to halt with file system mountedfrom global zone [2326105]If zone halts without unmounting the file system, the zone goes to down state<strong>and</strong> does not halt with the zoneadm comm<strong>and</strong>s.
Change language