# xlv_mgr xlv_mgr> show all Volume Element: SPARE_VE Volume: BIG_VOLUME (complete)In this example, there are two top level objects, a volume element named SPARE_VE and a logical volume named BIG_VOLUME. The volume element is a top level object because it is not part of (attached to) any plex. Volume elements can be attached to a plex at a later time.
To display the complete hierarchy of a top level object, give the xlv_mgr command show object with the name of the object, for example:
xlv_mgr> show object BIG_VOLUME VOL BIG_VOLUME (complete) VE BIG_VOLUME.log.0.0 [active] start=0, end=8255, (cat)grp_size=1 /dev/dsk/dks1d2s15 (8256 blks) VE BIG_VOLUME.log.1.0 [active] start=0, end=8255, (cat)grp_size=1 /dev/dsk/dks1d3s15 (8256 blks) VE BIG_VOLUME.log.2.0 [active] start=0, end=8255, (cat)grp_size=1 /dev/dsk/dks1d4s15 (8256 blks) VE BIG_VOLUME.data.0.0 [active] start=0, end=3920223, (cat)grp_size=1 /dev/dsk/dks1d2s7 (3920224 blks) VE BIG_VOLUME.data.1.0 [active] start=0, end=3920223, (cat)grp_size=1 /dev/dsk/dks1d3s7 (3920224 blks) VE BIG_VOLUME.data.2.0 [active] start=0, end=3920223, (cat)grp_size=1 /dev/dsk/dks1d4s7 (3920224 blks)This output shows that BIG_VOLUME contains log and data subvolumes. Each subvolume has three plexes that have one volume element each.