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
Removing LUNs dynamically from an existing target ID
In this case, a group of LUNs is unmapped from the host HBA ports and an operating system device scan is issued. To add subsequent LUNs seamlessly, perform additional steps to cleanup the operating system device tree.
To remove LUNs dynamically from an existing target ID
- Prior to any dynamic reconfiguration, ensure that the dmp_cache_open tunable is set to
on
. This setting is the default.# vxdmpadm gettune dmp_cache_open
If the tunable is set to
off
, set the dmp_cache_open tunable toon
.# vxdmpadm settune dmp_cache_open=on
- Identify which LUNs to remove from the host. Do one of the following:
Use Storage Array Management to identify the Array Volume ID (AVID) for the LUNs.
If the array does not report the AVID, use the LUN index.
- For LUNs under VxVM, perform the following steps:
Evacuate the data from the LUNs using the vxevac command.
See the vxevac(1M) online manual page.
After the data has been evacuated, enter the following command to remove the LUNs from the disk group:
# vxdg -g diskgroup rmdisk da-name
If the data has not been evacuated and the LUN is part of a subdisk or disk group, enter the following command to remove the LUNs from the disk group. If the disk is part of a shared disk group, you must use the -k option to force the removal.
# vxdg -g diskgroup -k rmdisk da-name
- For LUNs using HP-UX LVM over DMP devices, remove the device from the LVM volume group.
# vgreduce vgname devicepath
- Using the AVID or LUN index, use Storage Array Management to unmap or unmask the LUNs you identified in step 2.
- Remove the LUNs from the vxdisk list. Enter the following command on all nodes in a cluster:
# vxdisk rm da-name
This is a required step. If you do not perform this step, the DMP device tree shows ghost paths.
- Clean up the HP-UX 11i v3 SCSI device tree for the devices that you removed in step 6.
This step is required. You must clean up the operating system SCSI device tree to release the SCSI target ID for reuse if a new LUN is added to the host later.
- Scan the operating system device tree.
- Use VxVM to perform a device scan. You must perform this operation on all nodes in a cluster. Enter one of the following commands:
# vxdctl enable
# vxdisk scandisks
- Refresh the DMP device name database using the following command:
# vxddladm assign names
- Verify that the LUNs were removed cleanly by answering the following questions:
Is the device tree clean?
Verify that the operating system metanodes are removed from the /dev directory.
Were all the appropriate LUNs removed?
Use the DMP disk reporting tools such as the vxdisk list command output to determine if the LUNs have been cleaned up successfully.
Is the vxdisk list output correct?
Verify that the vxdisk list output shows the correct number of paths and does not include any ghost disks.
If the answer to any of these questions is "No," return to step 5 and perform the required steps.
If the answer to all of the questions is "Yes," the LUN remove operation is successful.