Contained WithinFind More DocumentationFeatured Support Resources |  PDF로 이 문서 다운로드 (1051 KB)
Chapter 6 State Database (Tasks)This chapter provides information about performing tasks that are associated with Solaris Volume Manager state database replicas. For information about the concepts involved in these tasks, see Chapter 5, State Database (Overview). State Database Replicas (Task Map)The following task map identifies the procedures needed to manage Solaris Volume Manager state database replicas.
Creating State Database Replicas Caution – If you upgraded from Solstice DiskSuiteTMto Solaris Volume Manager and you have state database replicas sharing slices with file systems or logical volumes (as opposed to on separate slices), do not delete existing replicas and replace them with new default replicas in the same location. The default state database replica size in Solaris Volume Manager is 8192 blocks, while the default size in Solstice DiskSuite was 1034 blocks. If you delete a default-sized state database replica from Solstice DiskSuite, and then add a new default-sized replica with Solaris Volume Manager, you will overwrite the first 7158 blocks of any file system that occupies the rest of the shared slice, thus destroying the data. How to Create State Database Replicas
Note – The metadb command without options reports the status of all replicas. Example—Creating the First State Database Replica
The -a option adds the additional state database replica to the system, and the -f option forces the creation of the first replica (and may be omitted when you add supplemental replicas to the system). Example—Adding Two State Database Replicas to the Same Slice
The -a option adds additional state database replicas to the system. The -c 2 option places two replicas on the specified slice. The metadb command checks that the replicas are active, as indicated by the -a. You can also specify the size of the state database replica with the -l option, followed by the number of blocks. However, the default size of 8192 should be appropriate for virtually all configurations, including those configurations with thousands of logical volumes. Example—Adding State Database Replicas of Specific SizeIf you are replacing existing state database replicas, you might need to specify a replica size. Particularly if you have existing state database replicas (on a system upgraded from Solstice DiskSuite, perhaps) that share a slice with a file system, you must replace existing replicas with other replicas of the same size or add new replicas in a different location. Caution – Do not replace default-sized (1034 block) state database replicas from Solstice DiskSuite with default-sized Solaris Volume Manager replicas on a slice shared with a file system. If you do, the new replicas will overwrite the beginning of your file system and corrupt it.
The -a option adds the additional state database replica to the system, and the -l option specifies the length in blocks of the replica to add. Maintaining State Database ReplicasHow to Check the Status of State Database Replicas
To check the status of state database replicas, use one of the following methods: Example—Checking the Status of All State Database Replicas
A legend of all the flags follows the status. The characters in front of the device name represent the status. Uppercase letters indicate a problem status. Lowercase letters indicate an “Okay” status. How to Delete State Database ReplicasYou might need to delete state database replicas to maintain your Solaris Volume Manager configuration. For example, if you will be replacing disk drives, you would want to delete the state database replicas before you remove the drives so they are not considered to have errors by Solaris Volume Manager. How to Delete State Database Replicas
Example—Deleting State Database Replicas
This example shows the last replica being deleted from a slice. Note – You must add a -f option to force deletion of the last replica on the system. |
|||||||||||||||||||
|