The metastat command shows transactional volumes, including both master devices and log devices. For each device, the following information is displayed:
“Device”, which is the device name of the slice or volume
“Start Block”, which is the block on which the device begins
“Dbase”, which shows if the device contains a state database replica
The following table explains transactional volume states and possible actions to take.
Table 18–1 Transactional Volume States
State |
Meaning |
Action |
---|---|---|
Okay |
The device is functioning properly. If mounted, the file system is logging and will not be checked at boot. |
None. |
Attaching |
The log device will be attached to the transactional volume when the volume is closed or unmounted. When this occurs, the device transitions to the Okay state. |
None. |
Detached |
The transactional volume does not have a log device. All benefits from UFS logging are disabled. |
The fsck command automatically checks the device at boot time. See the fsck(1M)man page. |
Detaching |
The log device will be detached from the transactional volume when the volume is closed or unmounted. When this occurs, the device transitions to the Detached state. |
None. |
Hard Error |
A device error or panic has occurred while the device was in use. An I/O error is returned for every read or write until the device is closed or unmounted. The first open causes the device to transition to the Error state. |
Fix the transactional volume. See How to Recover a Transactional Volume With a Panic, or How to Recover a Transactional Volume With Hard Errors. |
Error |
The device can be read and written to. The file system can be mounted read-only. However, an I/O error is returned for every read or write that actually gets a device error. The device does not transition back to the Hard Error state, even when a later device error occurs. |
Fix the transactional volume. See How to Recover a Transactional Volume With a Panic, or How to Recover a Transactional Volume With Hard Errors. Successfully completing the fsck or newfs commands transitions the device into the Okay state. When the device is in the Hard Error or Error state, the fsck command automatically checks and repairs the file system at boot time. The newfs command destroys whatever data might be on the device. |