Veritas Volume Manager 5.
Legal Notices © Copyright 2008 Hewlett-Packard Development Company, L.P. Publication Date: 2008 Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents Chapter 1 VxVM and LVM Introducing Veritas Volume Manager ................................................................ 7 Notable features of VxVM ............................................................................ 8 VxVM and LVM—conceptual comparison ........................................................10 Coexistence of VxVM and LVM disks ...............................................................
6 Contents Tasks with no direct LVM equivalents ............................................................. 66 Existing Features in LVM not supported in VxVM ......................................... 68 Chapter 4 SMH and the VEA Displaying disk devices in SMH ........................................................................ 70 Displaying volume groups and disk groups in SMH ...................................... 72 Displaying logical volumes in SMH ...............................................
Chapter 1 VxVM and LVM This chapter provides an overview of Veritas Volume Manager by Symantec (also referred to as VxVM) and its features. A brief description of the benefits of migrating from the HP-UX Logical Volume Manager (LVM) to VxVM, and the coexistence of VxVM disks with LVM disks is also given.
8 VxVM and LVM Introducing Veritas Volume Manager version of the ServiceGuard products. Refer to the Release Notes for details about the required version number, as well as the availability of specific features in your release. Notable features of VxVM The Veritas Volume Manager provides many features, some of which are not available with LVM or MirrorDisk/UX. Notable VxVM features are described in the list below.
VxVM and LVM Introducing Veritas Volume Manager ■ Mirrored stripes (RAID-0 + RAID-1) and striped mirrors (RAID-1 + RAID-0) combine the benefits of striping to improve performance by spreading data across multiple disks, and mirroring to provide redundancy of data. Striped mirror volumes are more tolerant of disk failure and have a shorter recovery time than mirrored stripe volumes. Refer to the Veritas Volume Manager Administrator’s Guide for more detailed information on these layouts.
10 VxVM and LVM VxVM and LVM—conceptual comparison VxVM and LVM—conceptual comparison The following section compares the terminology used in LVM and VxVM at a conceptual level. For more information, refer to the glossary of this Guide for precise and detailed definitions of these terms. Table 1-1 A conceptual comparison of LVM and VxVM LVM term VxVM term LVM VxVM Both LVM and VxVM enable online disk storage management. They both build virtual devices, called volumes, on physical disks.
VxVM and LVM VxVM and LVM—conceptual comparison Table 1-1 A conceptual comparison of LVM and VxVM LVM term VxVM term Volume group Disk group LVM volume groups are conceptually similar to VxVM disk groups. An LVM volume group is the collective identity of a set of physical volumes, which provide disk storage for the logical volumes. A VxVM disk group is a collection of VxVM disks that share a common configuration.
12 VxVM and LVM Coexistence of VxVM and LVM disks Table 1-1 A conceptual comparison of LVM and VxVM LVM term VxVM term Mirrors Mirrors (plexes) Both LVM and VxVM support mirrors. Mirrors can be used to store multiple copies of a volume’s data on separate disks. In LVM, you can create mirrors using the MirrorDisk/UX product. Mirrors allow duplicate copies of the extents to be kept on separate physical volumes. MirrorDisk/UX supports up to 3 copies of the data. A VxVM mirror consists of plexes.
VxVM and LVM Coexistence of VxVM and LVM disks Both LVM and VxVM utilities are aware of the other volume manager, and will not overwrite disks that are being managed by the other volume manager unless conversion or rollback is being performed between LVM logical volumes and VxVM volumes. The System Management Homepage (SMH) and Veritas Enterprise Administrator (VEA) graphical administrative utilities also recognize and identify all disks on the system. See “SMH and the VEA” on page 69.
14 VxVM and LVM Coexistence of VxVM and LVM disks
Chapter 2 Converting LVM to VxVM This chapter explains how to convert your LVM configuration to a VxVM configuration and presents the following main topics: ■ Converting unused LVM physical volumes to VxVM disks ■ Converting LVM volume groups to VxVM disk groups ■ Restoring the LVM volume group configuration ■ Examples The basic tools for conversion are the VxVM commands, vxvmconvert and vxdiskadm, and the LVM administrative utilities such as pvremove and vgcfgbackup.
16 Converting LVM to VxVM Converting unused LVM physical volumes to VxVM disks Converting unused LVM physical volumes to VxVM disks LVM disks which are not part of any volume group, and contain no user data, are simply cleaned up, so that there are no LVM disk headers. Then the disks are given over to VxVM through the normal means of initializing disks. Caution: Exercise caution while using this procedure to give disks over to VxVM.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Initializing disks for VxVM use To initialize the disk for VxVM use, use the vxdiskadm command, selecting the option: 1) Add or initialize one or more disks Or use the command: # vxdisk init disk_name VxVM utilities will not tamper with disks that are recognized as owned by LVM (by virtue of the LVM disk headers).
18 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Volume group conversion limitations There are certain LVM volume configurations that cannot be converted to VxVM. Some of the reasons a conversion could fail are: ■ A volume group with insufficient space for metadata. In the conversion of LVM to VxVM, the areas of the disks used to store LVM metadata are overwritten with VxVM metadata.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups ■ A volume group containing the /usr file system. For this release, a volume group containing the /usr file system cannot be converted because vxvmconvert needs access to files in /usr. ■ Volume groups with any dump or primary swap volumes. vxvmconvert will not convert any volume group with dump or primary swap volumes. These are volumes known to the boot process.
20 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Conversion process summary Several steps are used to convert LVM volume groups to VxVM disk groups. Most of these steps can be done with the vxvmconvert utility. All the steps are not compulsory, and some may have to be followed only if there are problems during conversion. Some of them (e.g. backing up user data) are left to you to accomplish through your regular administrative processes.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Conversion steps explained 1. Identifying LVM disks and volume groups for conversion The obvious first step in the conversion process is to identify what you want to convert. The native LVM administrative utilities like vgdisplay and SMH can help you identify candidate LVM volume groups as well as the disks that comprise them. You can also use the vxvmconvert and vxdisk commands to examine groups and their member disks.
22 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Note: The analysis option is presented as a separate menu item in vxvmconvert, but there is an implicit analysis with any conversion. If you simply select the “Convert LVM Volume Groups to VxVM” menu option, vxvmconvert will go through analysis on any group you specify. When you are using the convert option directly, you are given a chance to abort the conversion after analysis, and before any changes are committed to disk.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups You can back up the LVM volumes using the following command: # vgcfgbackup -f pathname/filename vol_grp_name Be sure to use the -f option to save the data into a file other than the default. vxvmconvert uses LVM utilities which themselves save the configuration using vgcfgbackup. If you do not use the -f option when you attempt to backup the configuration, the conversion process will overwrite your attempted backup.
24 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Non-file system back up If a logical volume you are converting does not contain a file system, and is being used directly by an application (such as a database application), use the backup facilities provided by the application. If no such facility exists, consider using the dd command. 5.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups This file provides information on how to proceed further to link the old LVM volume names to the new VxVM device names. Caution: This method of resolving the naming problem has risks. The symbolic links can become stale.
26 Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups Note: It is strongly recommended that you do not rely on vxvmconvert's mechanisms for unmounting file systems. Conversion will be simpler if you close applications, and unmount file systems before running vxvmconvert. To unmount a file system, use the following command: # umount file-system Conversion and reboot During conversion, after the analysis phase is complete, the disks to be converted are deemed to be conversion ready.
Converting LVM to VxVM Converting LVM volume groups to VxVM disk groups VxVM volume names, see “step 11. Tailoring your VxVM configuration,” on page 27. As described earlier in “step 2. Analyzing an LVM volume group to see if conversion is possible,” on page 21, the volume groups selected for conversion are analyzed to ensure that conversion is possible. After a successful analysis phase, vxvmconvert will ask you to commit to the change or abort the conversion.
28 Converting LVM to VxVM Restoring the LVM volume group configuration renames the LVM volume group by replacing the prefix vg in the volume group name with the prefix dg. For example, vg08 would become dg08. If there is no vg in the LVM volume group name, vxvmconvert simply uses the same volume group name for its disk group. The disks in the new VxVM disk group are given VxVM disk media names (see vxintro(1M)) based on this disk group name.
Converting LVM to VxVM Restoring the LVM volume group configuration Use rollback only if the VxVM configuration has not changed since the conversion. This method restores the LVM configuration without the need for user data restoration. See “Rollback to LVM using vxvmconvert” on page 30 for details on using this method.
30 Converting LVM to VxVM Restoring the LVM volume group configuration Rollback to LVM using vxvmconvert Rollback replaces the VxVM disk groups with the original LVM volume groups. During conversion, vxvmconvert saves a “snapshot” of the original LVM metadata and associated configuration files, such as /etc/fstab and LVM device files. It restores only the LVM metadata and configuration files from this snapshot; user data is not changed.
Converting LVM to VxVM Restoring the LVM volume group configuration Full LVM restoration If you need to restore the original LVM configuration, but changes have been made to the VxVM configuration, you cannot use the rollback option of vxvmconvert. In this case, you must restore the user data in addition to restoring the old LVM metadata and associated configuration files. You may need to use this method if the disks in use by the LVM/VxVM volumes were corrupted during or after conversion.
32 Converting LVM to VxVM Examples Examples Example: displaying the vxvmconvert menu To display the vxvmconvert menu, use the following command: # vxvmconvert The following menu is displayed: Volume Manager Support Operations Menu: Volume Manager/LVM_Conversion 1 2 3 list listvg ? ?? q Analyze LVM Volume Groups for Conversion Convert LVM Volume Groups to VxVM Roll back from VxVM to LVM List disk information List LVM Volume Group information Display help about menu Display help about the menuing system Exi
Converting LVM to VxVM Examples Example: listing LVM volume group information To list LVM volume group information, use the listvg option of vxvmconvert. Select the listvg option from the vxvmconvert Main Menu: Menu: Volume Manager/LVM_Conversion/ListLVMVolumeGroups # listvg Use this menu option to display a list of LVM volume groups. You can also choose to list detailed information about the LVM volume groups at a specific disk device address. Select the Volume Group as follows: Enter Volume Group (i.e.
34 Converting LVM to VxVM Examples LV Name LV Status LV Size (Mbytes) Current LE Allocated PE Used PV --- Physical volumes --PV Name PV Status Total PE Free PE /dev/vg08/lvol2 available/syncd 500 125 125 1 /dev/disk/disk12 available 250 0 List another LVM Volume Group? [y,n,q,?] (default: n) Select an operation to perform: Note: The volume groups you want to convert must not be a root volume group or have bootable volumes in the group.
Converting LVM to VxVM Examples listvg: list all LVM Volume Groups list: list all disk devices vg_name:a single LVM Volume Group, named vg_name :for example vg08 vg09 vg05 Select volume groups to analyze: [,all,list,listvg,q,?] vg08 Name a new disk group [,list,q,?] (default: dg08) Each volume group will be analyzed one at a time.
36 Converting LVM to VxVM Examples Use this operation to analyze one or more LVM volume groups for possible conversion using the VxVM Volume Manager. This operation checks for problems that would prevent the conversion from completing successfully. It calculates the space required to add the volume groups disks to a Volume Manager disk group, and to replace any existing partitions and volumes with Volume Manager volumes, plexes, and sub-disks.
Converting LVM to VxVM Examples the (vg08) Volume Group, and allowing that for every volume removed, the number of Database records required would be reduced by three. This is only a rough approximation, however. Hit RETURN to continue.
38 Converting LVM to VxVM Examples Select Volume Groups to convert : [,all,list,listvg,q,?] vg08 vg08 Convert this Volume Group? [y,n,q,?] (default: y) Name a new disk group [,list,q,?] (default: dg08) The following disk has been found in the vg08 volume group and will be configured for conversion to a VxVM disk group. disk12 A new disk group dg08 will be created and the disk device disk12 will be converted and added to the disk group with the disk name dg0801.
Converting LVM to VxVM Examples /dev/vg08/rlv2 will convert to /dev/vx/rdsk/vg08dg/dg08lv2 LVM Volume Group vg08 Records Saved Unmounting vg08 file systems Volume group "/dev/vg08" has been successfully changed. The Volume Manager is now reconfiguring (partition phase)... Volume Manager: Initializing disk12 as a converted LVM disk. The system reconfiguration will now be done without rebooting. The Volume Manager is now reconfiguring (initialization phase)...
40 Converting LVM to VxVM Examples :for example vg08 vg09 vg05 Select Volume Groups to convert : [,all,list,listvg,q,?] listvg LVM VOLUME GROUP INFORMATION NAME TYPE PHYSICAL VOLUME vg00 ROOT disk10 vg05 Non-Root disk11 vg03 Non-Root disk14 disk15 vg08 Non-Root disk12 Select Volume Groups to convert : [,all,list,listvg,q,?] vg08 vg08 Convert this Volume Group? [y,n,q,?] (default: y) Name a new disk group [,list,q,?] (default: dg08) The following disk has been fou
Converting LVM to VxVM Examples The smallest disk in the Volume Group (vg08) does not have sufficient private space for the conversion to succeed. There is only enough private space for 392 VM Database records and the conversion of Volume Group (vg08) would require enough space to allow 399 VxVM Database records. This would roughly translate to needing an additional 896 bytes available in the private space.
42 Converting LVM to VxVM Examples Example vxprint output before conversion TY NAME dg rootdg dm disk01 ASSOC rootdg c0t10d0 KSTATE - LENGTH PLOFFS 2079468 - STATE - TUTIL0 - PUTIL0 - The list and listvg output is from within the vxvmconvert command. vxprint is a command line command.
Converting LVM to VxVM Examples volume such as recovery and data access will be governed by the usage type fsgen. ■ The plex dg08lv1-01 is associated with volume dg08lv1, and maps the entire address range of the volume. Associated with the plex is one subdisk, dg0801-01 which maps the plex address range from 0 to the entire length of the plex, i.e. 102400 blocks. As implied by the root of its name, the subdisk dg0801-01 uses an extent from the VxVM disk dg0801.
44 Converting LVM to VxVM General information regarding conversion speed Selected Volume Groups have been restored. Hit RETURN to continue. Rollback other LVM Volume Groups? [y,n,q,?] (default: n) General information regarding conversion speed The speed of the process of converting an existing LVM volume group to a similar VxVM disk group is largely dependent upon the size of the volume group being converted, as well as on the complexity of the volumes within that volume group.
Converting LVM to VxVM Non-interactive conversion of volume groups same volume group (150GB) consisting of mirrored volumes that need to be synchronized can take 30-40 hours to convert. Note: If you convert mirrored volumes, you must synchronize them in a separate step. Non-interactive conversion of volume groups The vxvxconvert utility is an interactive command. You can also use the vxautoanalysis and vxautoconvert commands to perform non-interactive analysis and conversion of LVM volume groups.
46 Converting LVM to VxVM Non-interactive conversion of volume groups Converting volume groups to disk groups The vxautoconvert utility converts one or more LVM volume groups to VxVM disk groups. Any LVM extent-based striped volumes are converted to stripe-mirror (non-layered) VxVM volumes. Note: The VxVM configuration daemon (vxconfigd) must be running in order for the conversion to succeed. Conversion of the root volume group is not permitted. An error results if this is attempted.
Converting LVM to VxVM Non-interactive conversion of volume groups Converting disk groups back to volume groups The vxautorollback utility converts one or more VxVM disk groups back to the LVM volume groups from which they had previously been converted. Note: The VxVM configuration daemon (vxconfigd) must be running in order for the analysis to succeed. Reverse conversion is performed on each disk group in turn. Parallel conversion is not supported.
48 Converting LVM to VxVM Non-interactive conversion of volume groups
Chapter 3 Command differences This chapter describes the differences between LVM and VxVM commands, and tasks. It includes a task comparison chart which lists some of the tasks performed using LVM with a near equivalent task performed using VxVM. It also provides a list of VxVM tasks which are not available with LVM, and the LVM features currently not supported in VxVM.
50 Command differences LVM and VxVM command equivalents LVM and VxVM command equivalents The table below lists the LVM commands and a near equivalent command to use in VxVM. For more information, refer to the Task Comparison chart. For information on VxVM commands, refer to the Veritas Volume Manager documentation package. Table 3-1 Command comparison LVM Description/action VxVM Description/action lvchange Changes the characteristics of logical volumes.
Command differences LVM and VxVM command equivalents Table 3-1 Command comparison LVM Description/action VxVM Description/action lvreduce Decreases disk space allocated to a logical volume. vxassist Decreases a volume in size with the shrinkto or shrinkby parameters. Example: vxassist shrinkto vol_name 200M Make sure you shrink the file system before shrinking the volume. lvremove Removes one or more vxedit logical volumes from a volume group. Removes volumes with the -rf rm parameters.
52 Command differences LVM and VxVM command equivalents Table 3-1 Command comparison LVM Description/action VxVM lvsync Synchronizes vxrecover mirrors that are stale in one or more logical vxvol start volumes. Description/action The vxrecover command performs resynchronize operations for the volumes, or for volumes residing on the named disks (medianame or the VxVM name for the disk). Example: vxrecover vol_name media_name pvcreate Makes a disk an LVM disk.
Command differences LVM and VxVM command equivalents Table 3-1 Command comparison LVM Description/action VxVM pvmove Moves allocated vxevac physical extents from source to destination vxsd mv within a volume group. vxdiskadm Description/action Moves volumes off a disk. Performs volume operations on a subdisk. Moves the contents of old subdisk onto the new subdisks and replaces old sub disk with the new subdisks for any associations.
54 Command differences LVM and VxVM command equivalents Table 3-1 Command comparison LVM Description/action VxVM Description/action vgreduce Reduces a volume group by removing one or more disks from it. vxdg rmdisk Removes disks from a disk group. vxdisk rm Removes the specified disk access record by disk access name. vxdiskadm Option 3 in the vxdiskadm menu removes disks. vxinfo Displays information about volumes.
Command differences LVM and VxVM command equivalents Table 3-1 LVM lvchange, lvextend, lvcreate, lvreduce Command comparison Description/action VxVM Description/action No LVM command vxplex Operates on plex objects. Performs operations on logical volumes. vxvol Operates on volume objects. No LVM command vxsd Operates on subdisk objects. No LVM command vxmend Fixes simple misconfigurations.
56 Command differences Comparison of LVM and VxVM tasks Comparison of LVM and VxVM tasks This section contains a list of tasks which you can perform using LVM, and near equivalent tasks which you can perform using Veritas Volume Manager. You can perform the LVM tasks by using SMH or the command line interface. Similarly, you can choose to perform VxVM tasks by using the Veritas Enterprise Administrator (VEA) or the command line interface. This document focuses on the command line interface.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example VxVM Create a disk group. vxdg init disk_group disk_name Option 1 in the vxdiskadm menu performs this task. LVM Add a new disk to the existing volume group. vgextend /dev/vol_grp /dev/rdsk/ disk_name VxVM Add a disk to an existing disk group.
58 Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example LVM Extend a logical volume or increase lvextend -l 50 /dev/vol_grp/ space allocated to a logical volume. lvol_name l—indicates the number of logical extents in the logical volume VxVM Increase the volume by or to a given length.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example LVM Export and deactivate an LVM volume group, and its associated logical volumes. vgchange -a n vol_group vgexport /dev/vol_group VxVM Deport a disk group to disable vxdg deport disk_group access to the specified disk group. A disk group cannot be deported if Option 9 in the vxdiskadm menu any volumes in the disk group are performs this task. currently open.
60 Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example LVM Extend a volume group by adding LVM disks to the volume group. vgextend /dev/vol_grp/\ /dev/dsk/ disk_name VxVM Add one or more disks to the disk group. vxdiskadd disk_name Option 1 in the vxdiskadm main menu performs this task.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example VxVM Mirroring the VxVM root disk. vxrootmir [-v] [-t tasktag] disk_access_name | disk_media_name LVM Create a logical volume in LVM volume group.
62 Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example LVM Display information about volume groups. vgdisplay -v /dev/vol_grp VxVM Display disk group information. vxdisk list Display information about a specific disk group. vxprint -g disk_group vxdg list vxdisk list disk_group LVM Display information about physical pvdisplay /dev/dsk/disk_name volumes. VxVM Display information about Volume Manager volumes.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description LVM Set up alternate links to a physical volume. If a disk has two controllers, you can make one primary and the other an alternate link.
64 Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example LVM Increase the number of mirror copies. lvextend -m 2 /dev/vol_grp/ lvol_name VxVM Add mirrors to a volume or increase vxassist mirror vol_name the number of plexes. LVM Convert a mirrored logical volume into two logical volumes. Split a logical volume. lvsplit -s backup /dev/vol_grp/ lvol_name VxVM Snapshot a volume and create a new volume.
Command differences Comparison of LVM and VxVM tasks Table 3-2 LVM and VxVM task comparison Task type Description Example VxVM Resynchronize operations for the named volumes, or for volumes residing on the named disks. vxrecover -s vol_name If no medianame or volume operands are specified, then the operation applies to all volumes. LVM Start a volume. lvchange -a y /dev/vol_grp/ lvol_name VxVM Start a volume. vxrecover -s vol_name vxvol start vol_name LVM Stop a volume.
66 Command differences Tasks with no direct LVM equivalents Tasks with no direct LVM equivalents The following table lists tasks which have no direct LVM equivalent. Most of these tasks can be performed either with the Veritas Enterprise Administrator (VEA) GUI, or the command line interface. For more information, refer to the Veritas Enterprise Administrator User’s Guide and the Veritas Volume Manager Administrator’s Guide.
Command differences Tasks with no direct LVM equivalents Table 3-3 Additional VxVM tasks with no LVM equivalents Task description Example Recover a volume. vxrecover -g disk_group volume medianame vxmend fix clean plex_name Repair a mirror vxplex att plex_name Disable a mirror vxplex det plex_name Remove a log from a volume. vxassist remove log vol_name Move a subdisk.
68 Command differences Existing Features in LVM not supported in VxVM Existing Features in LVM not supported in VxVM Some of the existing features in LVM are not supported in the current release of VxVM. Given below is a table with the unsupported LVM features, and possible workarounds in VxVM. Table 3-4 LVM features and VxVM equivalents LVM Feature VxVM Equivalent Physical volume groups VxVM has no equivalent feature.
Chapter 4 SMH and the VEA This chapter describes the Veritas Enterprise Administrator (VEA) graphical user interface (GUI), and its relationship with the System Management Homepage (SMH). The following topics are discussed in this chapter: ■ Displaying disk devices in SMH ■ Displaying volume groups and disk groups in SMH ■ Displaying logical volumes in SMH SMH and the VEA coexist as independent entities. The VEA recognizes and labels LVM volumes and disks, but does not manage them.
70 SMH and the VEA Displaying disk devices in SMH Displaying disk devices in SMH To display disk devices in SMH, select Tools > Disks and File Systems > Disks. The Disks tab of the HP-UX Disks and File Systems Tool screen lists the system’s disk devices. To switch between legacy device names and new agile device names, click on Toggle Global Device View: In the legacy view, all paths to a device are listed using the old-style c#t#d# naming convention that is used in the /dev/dsk and /dev/rdsk directories.
SMH and the VEA Displaying disk devices in SMH Figure 4-1 Displaying disk devices in SMH 71
72 SMH and the VEA Displaying volume groups and disk groups in SMH Displaying volume groups and disk groups in SMH To display volume groups and disk groups in SMH, select Tools > Disks and File Systems > Volume Groups. The Volume Groups screen lists all the LVM volume groups and VxVM disk groups that are on the system. A more detailed description of a volume group’s properties can be obtained by selecting the radio button to the left of a listed volume group or disk group.
SMH and the VEA Displaying logical volumes in SMH Displaying logical volumes in SMH To display logical volumes in SMH, select Tools > Disks and File Systems > Logical Volumes. The Logical Volumes screen lists the LVM logical volumes and VxVM volumes on the system. The “Type” column indicates whether a volume is controlled by LVM or VxVM. The “Use” column shows whether a volume is in use and if so, what it is used for.
74 SMH and the VEA Displaying logical volumes in SMH Figure 4-3 Displaying LVM logical volumes and VxVM volumes in SMH
Appendix A Conversion error messages This appendix lists the error messages that you may encounter when conversting LVM volume groups to VxVM disk groups and volumes. For each error message, a description is provided of the problem, and the action that you can take to troubleshoot it. Table A-1 shows the error messages that you may encounter during conversion.
76 Conversion error messages Table A-1 Conversion error messages Message Description Device device_name has the following bad blocks... Cannot convert LVM Volume Group Unlike LVM, VxVM does not support bad block revectoring at the physical volume level. If there appear to be any valid bad blocks in the bad block directory (BBDIR) of any disk used in an LVM volume group, the group cannot be converted.
Conversion error messages Table A-1 Conversion error messages Message Description The conversion process was unable to deactivate the volume group vol_grp_name This indicates that the conversion process cannot deactivate the volume group. This Volume Group contains one or more logical volumes with mirrored data If you attempt to convert a Mirrored LVM Volume Group without a valid VxVM license installed, the conversion is not allowed. The conversion cannot be completed without rebooting the machine.
78 Conversion error messages Table A-1 Conversion error messages Message Description vxdiskadm or vxconvert is already being run and these programs cannot run concurrently The system detects that the vxdiskadd or vxconvert program is already running. Retry at a later time. Otherwise, if you are certain that no other users are running either of these programs, remove the file .DISKADD.LOCK from the /var/spool/locks directory to allow you to run vxconvert.
Glossary block A unit of space for data on a disk, typically having a size of 1024-bytes. Dirty Region Logging Dirty Region Logging (DRL) is an optional property of a volume, used to provide a speedy recovery of mirrored volumes after a system failure. DRL keeps track of the regions that have changed due to I/O writes to a mirrored volume. file system The organization of files on storage devices.
80 Glossary A MirrorDisk/UX mechanism whose use is optional, that tracks outstanding mirror write requests and provides a basis for the resynchronization of data blocks after a system crash or power failure. physical volume A disk that has been initialized by LVM becomes known as a physical volume. public region A region of a physical disk managed by VxVM that contains available space and is used for allocating subdisks.
Index A alternate links 63 B back up volume group 59 Backup vgcfgbackup 22 C coexistence VxVM and LVM disks 12 commands vxedit 50 configuration LVM 15 configuration VxVM 15 conversion errors 75 non-interactive 45 speed 44 D deactivate disk group 59 volume group 59 deport disk group 59 destroy disk group 59 disable mirror 67 disk evacuate 66 offline 66 online 66 recover 66 rename 66 replace 66 disk group 57 rename 66 disk groups 7 disk headers 17 disks 7 coexistence 12 mirroring 60 display disk group 61
82 Index and these programs cannot run concurrently 78 Example analyze LVM groups 32 conversion 32 failed coversion 32 list 32 list disk information 32 list LVM volume group information 32 listvg 32 VLM to VxVM 32 vxprint output 32 example Failed Analysis 32 export volume group 59 extend volume group 60 F File System 23 file system 58 G L list LVM 33 Logical Volume 10, 11 logical volume convert 64 split 64 synchronize 64 Logical Volume Manager 7 lvchange 50 lvcreate 50 lvextend 50 lvlnboot 50 LVM 7 meta
Index O T Online Migration 56 tools vxautoanalysis 15 vxautoconvert 15 vxautorollback 15 vxdiskadm 15 vxvmconvert 15 troubleshoot errors 75 P physical volumes 10, 11 Private Region 11 pvchange 52 pvcreate 52 pvdisplay 52 pvmove 53 R RAID-5 56 reduce 58 volume group 60 remove disk 62 volume 62 volume group 59, 62 rename disk group 66 repair mirror 67 restore volume group 59 resynchronize volumes 64 root disk configuring for VxVM 18 reconfiguring for LVM 18 root disks mirroring 60 rootability configurin
84 Index VxVM 7 features 8 metadata 18 VxVM names symbolic link 25 VxVM volumes resynchronize 64 vxvol 52, 55
