Stopping non-global zones configured with direct-mount file systems from outside VCS causes the corresponding zone resource to fault or go offline

Last published : Jun 10, 2026
Stopping non-global zones, which are configured with direct-mount file systems, from outside VCS causes the corresponding zone resource to fault or to go offline. The status of the zone shows down and the corresponding zone resource faults or goes offline. As a result, VCS cannot bring the zone resource online.
Workaround:
  1. Log into the global zone as the root user.
  2. Unmount the mount points that were in use by the zone and are still mounted:
    \# umount -o mntunlock=VCS /mount_point
    1. Stop the zone:
    \# zoneadm -z zone_name halt
This changes the status of the non-global zone to installed or configured.