< Previous  | TOC | Index | Next  >

Run convertname

The convertname utility takes Solaris Volume Manager device paths as arguments (metadevice paths or raw disk paths) and returns the VxVM volume path for the device as it will show after the conversion. Use the command to make a list of path names for replacing references in applications. One or more device paths as arguments returns one line for each argument with the proposed VxVM path. Use absolute path names. For example:

# convertname /dev/md/dsk/d2 /dev/md/rdsk/d3

Examples of the translation of device path names shows examples of how names are translated by the conversion process:

The following metadevices do not retain their dN names or are converted from raw partitions that did not have dN names:

• The volume for the root file system is always named rootvol as a VxVM convention.
• A trans metadevice has its data device converted using the master device name. The log device is lost.
• A file system encapsulated from a raw partition is named for the last component of its mount point.
• A swap device on a disk that will include VxVM volumes after the conversion receives a name starting with swapvol.
• The /usr, /opt, and /var file systems when converted from being Solaris Volume Manager metadevices or when encapsulated retain the names /usr, /opt, and /var.
  Warning: Any partition that is on a disk with Solaris Volume Manager metadevices and that is not listed as a file system in /etc/vfstab is lost during the conversion. The partition is considered free space when the disk is converted to VxVM control. Even if the partitions are in use, such as for Oracle raw tablespace data, they are not encapsulated during the conversion. The raw partitions are lost when the disk layout changes. Either encapsulate the partition under the Solaris Volume Manager software and allow the conversion to convert the resulting metadevice, or back up the partition, plan to create a new volume for it, and restore the partition after the conversion.