Some Veritas Volume Manager operations can cause volume device names to go out of sync


Some Veritas Volume Manager operations can cause volume device names to go out of sync
Prev	Software limitations of Storage Foundation support of non-global zones	Next

If a volume is exported to a non-global zone, some Veritas Volume Manager operations can cause the global and non-global volume device names to go out of sync, which can create data corruption. This is because the Solaris operating environment zone support is not aware of the devfsadm(1M) command, and thus the zone configuration is not updated with any changes to the /dev or /devices namespaces.

The following operations can cause device names to go out of sync:

Removing a volume
Importing a disk group
Deporting a disk group
Renaming a disk group or volume
Reminoring a disk group
Restarting vxconfigd or resetting the kernel

To prevent device names from to going out of sync, if a volume is exported to a non-global zone and an operation that can cause device names to go out of sync occurs on that volume, remove the volume from the zone configuration using the zonecfg command and reboot the zone using the zoneadm command.

See the zonecfg(1M) and zoneadm(1M) manual pages.

Note:

This issue applies to any Solaris device for which the /dev or /devices device node is changed and has been configured in the non-global zone before the change, including Solaris Volume Manager volumes.

Prev	Up	Next
Root volume cannot be added to non-global zones	Home	Storage Foundation and High Availability Solutions support for Branded Zones