Veritas™ Volume Manager Administrator's Guide
- Understanding Veritas Volume Manager
- VxVM and the operating system
- How VxVM handles storage management
- Volume layouts in VxVM
- Online relayout
- Volume resynchronization
- Dirty region logging
- Volume snapshots
- FastResync
- Provisioning new usable storage
- Administering disks
- Disk devices
- Discovering and configuring newly added disk devices
- Discovering disks and dynamically adding disk arrays
- How to administer the Device Discovery Layer
- Changing the disk-naming scheme
- Adding a disk to VxVM
- Rootability
- Displaying disk information
- Removing disks
- Removing and replacing disks
- Administering Dynamic Multi-Pathing
- How DMP works
- Administering DMP using vxdmpadm
- Gathering and displaying I/O statistics
- Specifying the I/O policy
- Online dynamic reconfiguration
- Reconfiguring a LUN online that is under DMP control
- Creating and administering disk groups
- About disk groups
- Displaying disk group information
- Creating a disk group
- Importing a disk group
- Moving disk groups between systems
- Handling cloned disks with duplicated identifiers
- Handling conflicting configuration copies
- Reorganizing the contents of disk groups
- Destroying a disk group
- Creating and administering subdisks and plexes
- Displaying plex information
- Reattaching plexes
- Creating volumes
- Types of volume layouts
- Creating a volume
- Using vxassist
- Creating a volume on specific disks
- Creating a mirrored volume
- Creating a striped volume
- Creating a volume using vxmake
- Initializing and starting a volume
- Using rules and persistent attributes to make volume allocation more efficient
- Administering volumes
- Displaying volume information
- Monitoring and controlling tasks
- Reclamation of storage on thin reclamation arrays
- Stopping a volume
- Resizing a volume
- Adding a mirror to a volume
- Preparing a volume for DRL and instant snapshots
- Adding traditional DRL logging to a mirrored volume
- Enabling FastResync on a volume
- Performing online relayout
- Adding a RAID-5 log
- Creating and administering volume sets
- Configuring off-host processing
- Administering hot-relocation
- How hot-relocation works
- Moving relocated subdisks
- Administering cluster functionality (CVM)
- Overview of clustering
- Multiple host failover configurations
- CVM initialization and configuration
- Dirty region logging in cluster environments
- Administering VxVM in cluster environments
- Changing the CVM master manually
- Importing disk groups as shared
- Administering sites and remote mirrors
- About sites and remote mirrors
- Fire drill - testing the configuration
- Changing the site name
- Administering the Remote Mirror configuration
- Failure and recovery scenarios
- Performance monitoring and tuning
- Appendix A. Using Veritas Volume Manager commands
- Appendix B. Configuring Veritas Volume Manager
Displaying the paths to a disk
The vxdisk command is used to display the multi-pathing information for a particular metadevice. The metadevice is a device representation of a particular physical disk having multiple physical paths from one of the system's HBA controllers. In DMP, all the physical disks in the system are represented as metadevices with one or more physical paths.
To display the multi-pathing information on a system
- Use the vxdisk path command to display the relationships between the device paths, disk access names, disk media names and disk groups on a system as shown here:
# vxdisk path
SUBPATH DANAME DMNAME GROUP STATE c1t0d0 c1t0d0 mydg01 mydg ENABLED c4t0d0 c1t0d0 mydg01 mydg ENABLED c1t1d0 c1t1d0 mydg02 mydg ENABLED c4t1d0 c1t1d0 mydg02 mydg ENABLED . . .
This shows that two paths exist to each of the two disks, mydg01 and mydg02, and also indicates that each disk is in the ENABLED state.
To view multi-pathing information for a particular metadevice
- Use the following command:
# vxdisk list devicename
For example, to view multi-pathing information for c1t0d3, use the following command:
# vxdisk list c1t0d3
The output from the vxdisk list command displays the multi-pathing information, as shown in the following example:
Device: c1t0d3 devicetag: c1t0d3 type: simple hostid: system01 . . . Multipathing information: numpaths: 2 c1t0d3 state=enabled type=secondary c4t1d3 state=disabled type=primary
The numpaths line shows that there are 2 paths to the device. The next two lines in the "Multipathing information" section show that one path is active (state=enabled) and that the other path has failed (state=disabled).
The type field is shown for disks on Active/Passive type disk arrays such as the EMC CLARiiON, Hitachi HDS 9200 and 9500, Sun StorEdge 6xxx, and Sun StorEdge T3 array. This field indicates the primary and secondary paths to the disk.
The type field is not displayed for disks on Active/Active type disk arrays such as the EMC Symmetrix, Hitachi HDS 99xx and Sun StorEdge 99xx Series, and IBM ESS Series. Such arrays have no concept of primary and secondary paths.
- Alternately, you can use the following command to view multi-pathing information:
# vxdmpadm getsubpaths dmpnodename=devicename
For example, to view multi-pathing information for emc_clariion0_17, use the following command:
# vxdmpadm getsubpaths dmpnodename=emc_clariion0_17
Typical output from the vxdmpadm getsubpaths command is as follows:
NAME STATE[A] PATH-TYPE[M] CTLR-NAME ENCLR-TYPE ENCLR-NAME ATTRS =============================================================================== c0t5d7 ENABLED(A) PRIMARY c0 EMC_CLARiiON emc_clariion0 - c0t5d7 ENABLED(A) PRIMARY c0 EMC_CLARiiON emc_clariion0 - c0t5d7 ENABLED SECONDARY c0 EMC_CLARiiON emc_clariion0 -- c0t5d7 ENABLED SECONDARY c0 EMC_CLARiiON emc_clariion0 -