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
Changing subdisk attributes
Warning:
To avoid possible data loss, change subdisk attributes with extreme care.
The vxedit command changes attributes of subdisks and other VxVM objects. To change subdisk attributes, use the following command:
# vxedit [-g diskgroup] set attribute=value ... subdisk ...
The subdisk fields you can change with the vxedit command include the following:
Subdisk name. | |
Persistent utility field(s) used to manage objects and communication between different commands and Symantec products. putiln field attributes are maintained on reboot. putiln fields are organized as follows:
If a command is stopped in the middle of an operation, these fields may need to be cleaned up. | |
Nonpersistent (temporary) utility field(s) used to manage objects and communication between different commands and Symantec products. tutiln field attributes are not maintained on reboot. tutiln fields are organized as follows:
If a command is stopped in the middle of an operation, these fields may need to be cleaned up. | |
Subdisk length. This value is a standard Veritas Volume Manager length number. See the vxintro(1M) manual page. You can only change the length of a subdisk if the subdisk is disassociated. You cannot increase the length of a subdisk to the point where it extends past the end of the disk or it overlaps a reserved disk region on another disk. | |
Comment. |
For example, to change the comment field of a subdisk named mydg02-01 in the disk group, mydg, use the following command:
# vxedit -g mydg set comment="subdisk comment" mydg02-01
To prevent a particular subdisk from being associated with a plex, set the putil0 field to a non-null string, as shown in the following command:
# vxedit -g mydg set putil0="DO-NOT-USE" mydg02-01
See the vxedit(1M) manual page.