Planning for new VxVM logical volume names
| Article:HOWTO59676 | | | Created: 2011-10-14 | | | Updated: 2011-10-14 | | | Article URL http://www.symantec.com/docs/HOWTO59676 |
When you change from LVM volumes to VxVM volumes, the device names by which your system accesses data are changed. LVM creates device nodes for its logical volumes in /dev under directories named for the volume group. VxVM creates its device nodes in /dev/vx/dsk and /dev/vx/rdsk. When conversion is complete, the old LVM device nodes are gone from the system, and the system will access data on the device nodes in /dev/vx.
This change in names can present problems. Any application that refers to specific device node names will be at risk when these names change. Similarly, any files that record specific device node names for use by applications can be problematic.
The most obvious area where this problem arises is in /etc/fstab. To handle this problem, vxvmconvert will rewrite the fstab with the new VxVM names when conversion is done so that fsck, mount, and related utilities will behave as they did before the conversion.
There are potentially many other applications, though, that may be put at risk by the name changes in conversion. vxvmconvert cannot help with these. The system administrator must examine the mechanisms used in each of the following areas to see if they reference LVM device names:
See Workaround.
|
|
Legacy ID
uxrt-51sp1_id-SF270615217_v63475581
Article URL http://www.symantec.com/docs/HOWTO59676
Terms of use for this information are found in Legal Notices
Thank you.