Veritas Volume Manager 5.1 SP1 Administrator"s Guide (5900-1506, April 2011)

dm ibm_ds8x000_0267 ibm_ds8x000_0267 - 2027264 - - - -
dm ibm_ds8x000_0268 ibm_ds8x000_0268 - 2027264 - - - -
v vol1 fsgen ENABLED 409600 - ACTIVE - -
pl vol1-01 vol1 ENABLED 409600 - ACTIVE - -
sd ibm_ds8x000_0266-01 vol1-01 ENABLED 409600 0 - - -
pl vol1-02 vol1 ENABLED 409600 - ACTIVE - -
sd ibm_ds8x000_0267-01 vol1-02 ENABLED 409600 0 - - -
dc vol1_dco vol1 - - - - - -
v vol1_dcl gen ENABLED 144 - ACTIVE - -
pl vol1_dcl-01 vol1_dcl ENABLED 144 - ACTIVE - -
sd ibm_ds8x000_0266-02 vol1_dcl-01 ENABLED 144 0 - - -
pl vol1_dcl-02 vol1_dcl ENABLED 144 - ACTIVE - -
sd ibm_ds8x000_0267-02 vol1_dcl-02 ENABLED 144 0 - - -
The following vxassist command confirms that vol1 is in tier1. The application
of rule tier1 was successful.
vxassist -g dg3 listtag
TY NAME DISKGROUP TAG
=========================================================
v vol1 dg3 vxfs.placement_class.tier1
Using persistent attributes
You can define volume allocation attributes so they can be reused in subsequent
operations. These attributes are called persistent attributes, and they are stored
in a set of hidden volume tags. The persist attribute determines whether an
attribute persists, and how the current command might use or modify preexisting
persisted attributes. You can specify persistence rules in defaults files, in rules,
or on the command line. For more information, see the vxassist manual page.
To illustrate how persistent attributes work, we'll use the following vxsf_rules
files. It contains a rule, rule1, which defines the mediatype attribute. This rule
also uses the persist attribute to make the mediatype attribute persistent.
# cat /etc/default/vxsf_rules
volume rule rule1 { mediatype:ssd persist=extended }
The following command confirms that LUNs ibm_ds8x000_0266 and
ibm_ds8x000_0268 are solid-state disk (SSD) devices.
# vxdisk listtag
DEVICE NAME VALUE
Creating volumes
Using rules and persistent attributes to make volume allocation more efficient
332