PRIMECLUSTER Global Disk Services Configuration and Administration Guide 4.1 (Solaris(TM) Operating System)

A.2.32 Use of GDS in Solaris 10 Environments

When using Solaris Zones, GDS installation, command execution, and volume creation can be performed only in the global zone.
By importing GDS volumes created in the global zone to non-global zones, it becomes possible to use the GDS volumes in the non-global zones.

Understand and pay attention to the following points when using Solaris Zones.

• Install GDS in the global zone. GDS cannot be installed in a non-global zone.

• GDS commands cannot be executed in non-global zones. If GDS commands installed in the /usr/sbin directory in the global zone are executed in non-global zones, the following error occurs.

  ERROR: cannot be executed in non-global zone

  Depending on how non-global zones are created, if GDS command execution is attempted in non-global zones, an error message of ld.so.1(1) may be output.
  
  

• When the same block within a GDS volume is accessed simultaneously from multiple zones, data consistency is not ensured, as in access to slices that are not managed with GDS. Access exclusion control for maintaining data consistency should be performed by the application that accesses the same block from multiple zones.

  
  For the method for importing devices in the global zone to non-global zones, see the Solaris OS manual.