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
Background Information for Renaming Volumes
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
Background Information for Expanding Slices and Volumes
Overview of Replacing and Enabling Components in RAID-1 and RAID-5 Volumes
Replacing a Component With Another Available Component
Maintenance and Last Erred States
Background Information for 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
Solaris Volume Manager configuration files contain basic Solaris Volume Manager information, as well as most of the data that is necessary to reconstruct a configuration. The following procedures illustrate how to work with these files.
# metastat -p > /etc/lvm/md.tab
This file contains all parameters for use by the metainit command and metahs command. Use this file if you need to set up several similar environments or if you need to recreate the configuration after a system failure.
For more information about the md.tab file, see Overview of the md.tab File and the md.tab(4) man page.
On occasion, your system loses the information maintained in the state database. For example, this loss might occur if the system was rebooted after all of the state database replicas were deleted. As long as no volumes were created after the state database was lost, you can use the md.cf or md.tab files to recover your Solaris Volume Manager configuration.
Note - The md.cf file does not maintain information on active hot spares. Thus, if hot spares were in use when the Solaris Volume Manager configuration was lost, those volumes that were using active hot spares are likely corrupted.
For more information about these files, see the md.cf(4) and the md.tab(4) man pages.
See Creating State Database Replicas for more information.
If you are attempting to recover the last known Solaris Volume Manager configuration, copy the md.cf file into the /etc/lvm/md.tab file.
If you are creating a new Solaris Volume Manager configuration based on a copy of the md.tab file that have you preserved, copy the preserved file into the /etc/lvm/md.tab file.
If you are creating a new configuration or recovering a configuration after a crash, configure the mirrors as one-way mirrors. For example:
d80 -m d81 1 d81 1 1 c1t6d0s3
If the submirrors of a mirror are not the same size, be sure to use the smallest submirror for this one-way mirror. Otherwise, data could be lost.
If you are recovering an existing configuration and Solaris Volume Manager was cleanly stopped, leave the mirror configuration as multi-way mirrors. For example:
d70 -m d71 d72 1 d71 1 1 c1t6d0s2 d72 1 1 c1t5d0s0
Specify RAID-5 volumes with the -k option, to prevent reinitialization of the device. For example:
d45 -r c1t3d0s5 c1t3d0s3 c1t3d0s4 -k -i 32b
See the metainit(1M) man page for more information.
# metainit -n md.tab-entry
# metainit -n -a
The metainit command does not maintain a hypothetical state of the devices that might have been created while running with the -n, so creating volumes that rely on other, nonexistent volumes will result in errors with the -n even though the command may succeed without the -n option.
Specifies not to actually create the devices. Use this option to verify that the results are as you expected.
Specifies the name of the component to initialize.
Specifies to check all components.
# metainit -a
Specifies to activate the entries in the /etc/lvm/md.tab file.
# mettach mirror submirror
# metastat