How to Recreate a Stripe or Concatenation After Slice Failure (Command Line)

After checking the prerequisites ("Prerequisites for Maintaining DiskSuite Objects"), and the preliminary information ("Preliminary Information for Recreating a Stripe or Concatenation"), use the metaclear(1M) and metainit(1M) commands to recreate a stripe or concatenation after a slice has failed. The metastat command does not show slice errors for concatenations and stripes. You will, however, see errors on the system console, such as:

WARNING: md d35: read error on /dev/dsk/c0t0d0s6

Refer to the metaclear(1M) and metainit(1M) man pages for more information.

Example -- Recreating a Concatenation After Slice Failure

# umount /news
# init 0
ok boot -s
...
 
# ufsdump 0ucf /dev/rmt/0 /news
 
DUMP: Date of this level 0 dump: Fri Mar 1 15:17:45 1996
...
 
DUMP: DUMP IS DONE
# metaclear d35
# metainit d35 2 1 c1t0d0s2 1 c1t0d1s2
# newfs /dev/md/rdsk/d35
# mount /dev/md/dsk/d35 /news
# cd /news
# ufsrestore rvf /dev/rmt 0
Verify volume and initialize maps
Media block size is 126
...
Check pointing the restore
# rm restoresymtable
# ls /news

Because d35 contains a mounted file system, /news, it is unmounted, then the system is booted into single-user mode. The ufsdump command dumps data to tape, and the concatenation is cleared with the metaclear command. The metainit command recreates the concatenation using a new slice to replace the failed slice. Data is restored via the ufsrestore command, then validated, for example, by using the ls command.

If the metadevice is a stripe, the new slice must be the same size as the failed one. If the metadevice is a concatenation, the new slice must have at least the same capacity as the failed slice.