|
|||
1. Getting Started With Solaris Volume Manager 2. Storage Management Concepts 3. Solaris Volume Manager Overview 4. Solaris Volume Manager for Sun Cluster (Overview) 5. Configuring and Using Solaris Volume Manager (Scenario) 8. RAID-0 (Stripe and Concatenation) Volumes (Overview) 9. RAID-0 (Stripe and Concatenation) Volumes (Tasks) 10. RAID-1 (Mirror) Volumes (Overview) 11. RAID-1 (Mirror) Volumes (Tasks) 12. Soft Partitions (Overview) 16. Hot Spare Pools (Overview) 20. Maintaining Solaris Volume Manager (Tasks) Solaris Volume Manager Maintenance (Task Map) Viewing the Solaris Volume Manager Configuration How to View the Solaris Volume Manager Volume Configuration Working With Configuration Files How to Create Configuration Files How to Initialize Solaris Volume Manager From a Configuration File Changing Solaris Volume Manager Default Values Expanding a File System Using the growfs Command Overview of Replacing and Enabling Components in RAID-1 and RAID-5 Volumes 21. Best Practices for Solaris Volume Manager 22. Top-Down Volume Creation (Overview) 23. Top-Down Volume Creation (Tasks) 24. Monitoring and Error Reporting (Tasks) 25. Troubleshooting Solaris Volume Manager (Tasks) A. Important Solaris Volume Manager Files B. Solaris Volume Manager Quick Reference |
Renaming VolumesBackground Information for Renaming VolumesSolaris Volume Manager enables you to rename most types of volumes at any time, subject to some constraints. You can use either the Enhanced Storage tool within the Solaris Management Console or the command line (the metarename(1M) command) to rename volumes. Renaming volumes or switching volume names is an administrative convenience for the management of volume names. For example, you could arrange all file system mount points in a desired numeric range. You might rename volumes to maintain a naming scheme for your logical volumes or to allow a transactional volume to use the same name as the name of the underlying volume. Note - Transactional volumes are no longer valid in Solaris Volume Manager. You can rename transactional volumes to replace them. Before you rename a volume, make sure that it is not currently in use. For a file system, make sure that it is not mounted or being used as swap. Other applications that use the raw device, such as a database, should have their own way of stopping access to the data. Specific considerations for renaming volumes include the following:
Exchanging Volume NamesUsing the metarename command with the -x option exchanges the names of volumes that have a parent-child relationship. For more information, see How to Rename a Volume and the metarename(1M) man page. The name of an existing volume is exchanged with one of its subcomponents. For example, this type of exchange can occur between a mirror and one of its submirrors. The metarename -x command can make it easier to mirror or unmirror an existing volume. Note - You must use the command line to exchange volume names. This functionality is currently unavailable in the Solaris Volume Manager GUI. However, you can rename a volume with either the command line or the GUI. Consider the following guidelines when you want to rename a volume:
How to Rename a VolumeBefore You BeginCheck the volume name requirements (Volume Names), and Background Information for Renaming Volumes.
In the following example, the volume, d10, is renamed to d100. # umount /home # metarename d10 d100 d10: has been renamed to d100 (Edit the /etc/vfstab file so that the file system references the new volume) # mount /home Because d10 contains a mounted file system, the file system must be unmounted before the volume can be renamed. If the volume is used for a file system with an entry in the /etc/vfstab file, the entry must be changed to reference the new volume name. For example, if the /etc/vfstab file contains the following entry for the file system: /dev/md/dsk/d10 /dev/md/rdsk/d10 /docs home 2 yes - Change the entry to read as follows: /dev/md/dsk/d100 /dev/md/rdsk/d100 /docs home 2 yes - Then, remount the file system. If you have an existing mirror or transactional volume, you can use the metarename -x command to remove the mirror or transactional volume and keep data on the underlying volume. For a transactional volume, as long as the master device is a volume ( either a RAID-0, RAID-1, or RAID-5 volume), you can keep data on that volume. |
||
|