The metastat command displays the current status for each metadevice (including stripes, concatenations, concatenations of stripes, mirrors, RAID5, soft partitions, and trans devices) or hot spare pool, or of specified metadevices, components, or hot spare pools.
It is helpful to run the metastat command after using the metattach command to view the status of the metadevice.
Displays usage message.
Checks the status of all active metadevices and hot spares. The inquiry causes all components of each metadevice to be checked for accessibility, starting at the top level metadevice. When problems are discovered, the metadevice state databases are updated as if an error had occurred.
Displays the list of active metadevices and hot spare pools in the same format as md.tab.
Displays whether sub-devices are relocatable. At the end of the output, displays the devices and their associated device IDs.
Specifies the name of the diskset on which metastat will work. Using the -s option causes the command to perform its administrative function within the specified diskset. Without this option, the command performs its function on metadevices and/or hot spare pools in the local diskset.
Prints the current status and timestamp for the specified metadevices and hot spare pools. The timestamp provides the date and time of the last state change.
Displays the status of the component hosting a soft partition, including extents, starting blocks, and block count.
Displays the status of the specified hot spare pool(s).
Displays the status of the specified metadevice(s). If a trans metadevice is specified, the status of the master and log devices is also displayed.
The following example shows the partial output of the metastat command after creating a mirror, d0, consisting of two submirrors, d70 and d80.
# metastat d0 d0: Mirror Submirror 0: d80 State: Okay Submirror 1: d70 State: Resyncing Resync in progress: 15 % done Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 2006130 blocks . . .
The following example shows the partial output of the metastat command after creating a soft partition, d3, on concat d2, which is built on a soft partition.
# metastat d2: Concat/Stripe Size: 204800 blocks Stripe 0: Device Start Block Dbase State Hot Spare d0 0 No Okay d0: Soft Partition Component: c0t3d0s0 Status: Okay Size: 204800 blocks Extent Start Block Block count 0 129 204800 d3: Soft Partition Component: d2 Status: Okay Size: 202752 blocks Extent Start Block Block count 0 129 202752
metastat displays states as of the time the command is entered. It is unwise to use the output of the metastat -p command to create a md.tab(4) file for a number of reasons:
The output of metastat -p might show hot spares being used.
It might show mirrors with multiple submirrors. See metainit(1M) for instructions for creating multi-way mirrors using metainit and metattach.
A slice may go into an error state after metastat -p is issued.
See attributes(5) for descriptions of the following attributes:
|ATTRIBUTE TYPE||ATTRIBUTE VALUE|
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metareplace(1M), metaroot(1M), metaset(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), attributes(5)
Solaris Volume Manager Administration Guide