The / file system /dev/md/rdsk/d0 is being checked

For information on naming volumes, see Volume Names. Specifies the names of the components that are used. This example uses the root slice, c0t0d0s0.

Create a second RAID-0 volume concatenation on an unused slice c1t1d0s0 in this example to act as the second submirror. The second submirror must be the same size as the original submirror or larger. Use one of the following methods:. Specifies the name of the component that will be the first submirror in the mirror.

In this example, it is the RAID-0 volume that contains the root slice. See the metainit 1M man page for more information. When you create a mirror from an existing file system, you must follow the next two steps precisely to avoid data corruption. Any information pertaining to the master device is rolled from the log device prior to removing the trans metadevice.

Use this task to remove UFS logging from a file system that can be unmounted. Make sure you have met the prerequisites "Prerequisites for Removing DiskSuite Objects" and have read the preliminary information "Preliminary Information for Removing Trans Metadevices".

Because the file system is no longer a logging device, you must run fsck before you can mount it. You run fsck either on the raw metadevice or raw device for the slice, depending on the configuration of the master device.

Answer y to the following prompt:. If you are mounting the file system on a metadevice, run fsck on the raw device for that metadevice. Otherwise, run fsck on the raw device for slice upon which you will mount the file system. If the master and logging devices were metadevices, you should delete the metadevices that you no longer need. After checking the prerequisites "Prerequisites for Removing DiskSuite Objects" and the preliminary information "Preliminary Information for Removing Trans Metadevices" , use the metaclear 1M command to remove the trans metadevice.

Refer to the metaclear 1M man page for more information. When the trans metadevice is cleared, any information pertaining to the master device is rolled from the log prior to clearing the device. Make sure that the state database replica is no longer needed. Refer to the metadb 1M man page for more information. This example deletes a system's remaining two state database replicas. The -f option is needed. Any data that is on a metadevice is lost when it is removed from the system for good, and its underlying slices are reused.

Data should be backed up if you need to save it. If you delete a stripe or concatenation and reuse the slices that were part of the deleted metadevice, all data on the metadevice is gone from the system. Thus, make sure you back up the data on the metadevice before deleting it.

Make sure you have met the prerequisites "Prerequisites for Removing DiskSuite Objects" , and have read the preliminary information "Preliminary Information for Removing Stripes and Concatenations". For example, a file system on the metadevice should be unmounted. For a non-UFS application, such as a database, perform the steps necessary to stop the application's use of the metadevice. You do not want to confuse the system by asking it to mount a file system on a non-existent metadevice.

After checking the prerequisites "Prerequisites for Removing DiskSuite Objects" , and the preliminary information "Preliminary Information for Removing Stripes and Concatenations" , use the metaclear 1M command to delete the metadevice. Refer to the metaclear 1M man page for more information. This example clears the concatenation d8 that also contains a mounted file system.

The file system must be unmounted before the metadevice can be cleared. The system displays a confirmation message that the concatenation is cleared. To remove a mirror and keep the same metadevice name as the mount device, refer to "Metadevice Name Switching".

If you delete a mirror's submirrors and reuse the slices that were part of the deleted submirrors, all of that data is gone from the system. Thus, make sure you back up the data on the mirror before deleting it and its submirrors. When removing a mirror, you first "break apart" the mirror into its submirrors.

You can choose to keep the data on one of the submirrors, or if a submirror consists of a single slice, you can keep the data on the slice. Make sure you have met the prerequisites "Prerequisites for Removing DiskSuite Objects" , and have read the preliminary information "Preliminary Information for Removing Mirrors".

For example, a mirrored file system should be unmounted. After checking the prerequisites "Prerequisites for Removing DiskSuite Objects" , and the preliminary information "Preliminary Information for Removing Mirrors" , use the metadetach 1M and metaclear 1M commands to delete the metadevice.

Refer to the metadetach 1M and metaclear 1M man pages for more information. This example clears the mirror d2 that also contains a mounted file system.

The mirror consists of submirrors d0 and d1. The metastat command reports that both submirrors are in the "Okay" state.

The file system must be unmounted before the metadetach command detaches submirror d0 from mirror d2. The mirror is then cleared. It is remounted on d0. The other submirror, d1 , is cleared with the metaclear command. Any data that is on the RAID5 metadevice is lost when it is removed from the system for good, and its underlying slices are reused.

If you delete a RAID5 metadevice and reuse the slices that were part of the deleted device, all of that data is gone from the system. Thus, make sure you back up the data on the RAID5 metadevice before deleting it. For example, a file system should be unmounted. You do not want to confuse the system by asking it to mount a file system on a non-existent device. Access to d80 is stopped by unmounting its file system.

The system displays a confirmation message that the RAID5 metadevice is cleared. You do not want to confuse the system by attempting to mount a file system on a non-existent metadevice.

This section describes how to remove trans metadevices UFS logging. To remove a trans metadevice and keep the same metadevice name as the mount device, refer to "Metadevice Name Switching". Removing a trans metadevice removes logging from the appropriate file systems. The underlying data and possibly a metadevice, if the master consists of one on the file systems is still preserved, unless you also remove that metadevice or remove the slice.

Any information pertaining to the master device is rolled from the log device prior to removing the trans metadevice. Use this task to remove UFS logging from a file system that can be unmounted. In this example, disk2 is that alternate boot device. In this example, the metastat command shows that the following submirrors need maintenance:.

Halt the system, replace the disk. Use the format command or the fmthard command, to partition the disk as it was before the failure. If the new disk is identical to the existing disk the intact side of the mirror, in this example , quickly format the new disk. You should have recorded the alternate boot device when you created the mirror. To delete the failed state database replicas and then add them back, use the metadb command. Re-enable the submirrors by using the metareplace command.