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
Handling of minor number conflicts
The volume device minor numbers in a disk group to be imported may conflict with existing volume devices. In previous releases of VxVM, the conflicts resulted in failures. Either the disk group import operation failed, or the slave node failed to join a shared disk group. When this situation happened, you had to run the vxdg reminor command manually to resolve the minor conflicts. Starting with this release, VxVM can automatically resolve minor number conflicts.
If a minor conflict exists when a disk group is imported, VxVM automatically assigns a new base minor to the disk group, and reminors the volumes in the disk group, based on the new base minor. You do not need to run the vxdg reminor command to resolve the minor conflicts.
To avoid any conflicts between shared and private disk groups, the minor numbers are divided into shared and private pools. VxVM allocates minor numbers of shared disk groups only from the shared pool, and VxVM allocates minor numbers of private disk groups only from the private pool. If you import a private disk group as a shared disk group or vice versa, the device minor numbers are re-allocated from the correct pool. The disk group is dynamically reminored.
By default, private minor numbers range from 0-32999, and shared minor numbers start from 33000. You can change the division, if required. For example, you can set the range for shared minor numbers to start from a lower number. This range provides more minor numbers for shared disk groups and fewer minor numbers for private disk groups.
Normally, the minor numbers in private and shared pools are sufficient, so there is no need to make changes to the division.
Note:
To make the new division take effect, you must run vxdctl enable or restart vxconfigd after the tunable is changed in the defaults file. The division on all the cluster nodes must be exactly the same to prevent node failures for node join, volume creation, or disk group import operations.
To change the division between shared and private minor numbers
- Add the tunable sharedminorstart to the defaults file
/etc/default/vxsf
. For example, to change the shared minor numbers so that the range starts from 20000, set the following line in the/etc/default/vxsf
file.sharedminorstart=20000
You cannot set the shared minor numbers to start at less than 1000. If
sharedminorstart
is set to values between 0 to 999, the division of private minor numbers and shared disk group minor numbers is set to 1000. The value of 0 disables dynamic renumbering. - Run the following command:
# vxdctl enable
In certain scenarios, you may need to disable the division between shared minor numbers and private minor numbers. For example, you may need to prevent the device minor numbers from being changed when you upgrade from a previous release. In this case, disable the dynamic reminoring before you install the new VxVM package.
To disable the division between shared and private minor numbers
- Set the tunable sharedminorstart in the defaults file
/etc/default/vxsf
to 0 (zero). Set the following line in the/etc/default/vxsf
file.sharedminorstart=0
- Run the following command:
# vxdctl enable