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
Creating a volume on SSD devices
This section explains how to create a volume on Solid State Disk (SSD) device.
You must upgrade the disk group to version 150 or higher for SSD support. To upgrade the disk group, use the following command:
# vxdg upgrade diskgroup
where diskgroup
is the name of the disk group to which the disk belongs.
The allocation behavior of the vxassist command changes with the presence of SSD devices in a disk group.
Note:
If the disk group version is less than 150, the vxassist command does not honor media type of the device for making allocations.
The vxassist command allows you to specify Hard Disk Drive (HDD) or SSD devices for allocation using the mediatype
attribute. For example, to create a volume myvol
of size 1g on SSD disks in mydg
, use the following command:
# vxassist -g mydg make myvol 1g mediatype:ssd
For example, to create a volume myvol
of size 1g on HDD disks in mydg
, use the following command:
# vxassist -g mydg make myvol 1g mediatype:hdd
If neither mediatype:hdd
nor mediatype:ssd
is specified, then mediatype:hdd
is considered as default selection type which means only the HDD devices present in the disk group are considered for allocation.
If a mix of SSD devices and HDD devices are specified, the allocation is done only on HDD devices unless mediatype:ssd is explicitly specified. For example:
enclr1 : enclosure having all SSD devices enclr2 : enclosure having all HDD devices enclr3 : enclosure having mix of SSD and HDD devices
In the following command, volume myvol
of size 1G is allocated on devices from enclr2
array (only HDD devices):
# vxassist -g mydg make myvol 1G enclr:enclr1 enclr:enclr2
In order to create a volume on SSD devices from enclr1
enclosure, following command should be used:
# vxassist -g mydg make myvol 1G enclr:enclr1 mediatype:ssd
If enclr3
is only specified, only hdd devices present in enclr3 are considered for allocation.
In the following two commands, volume myvol of size 1G is allocated on HDD devices from enclr3 array:
# vxassist -g mydg make myvol 1G enclr:enclr3 mediatype:hdd # vxasisst -g mydg make myvol 1G enclr:enclr3
In order to allocate a volume on SSD devices from enclr3 enclosure, following command should be used:
# vxassist -g mydg make myvol 1G enclr:enclr3 mediatype:ssd
The allocation fails, if the command is specified in one of the following two ways:
# vxassist -g mydg make myvol 1G enclr:enclr1 mediatype:hdd
In the above case, volume myvol
cannot be created as there are no HDD devices in enclr1
enclosure.
# vxassist -g mydg make myvol 1G enclr:enclr2 mediatype:ssd
In the above case, volume myvol cannot be created as there are no SSD devices in enclr2
enclosure.