1. Replace and partition the disk if it has failed.

2. Because the system cannot be booted from the boot disk, boot from the CD-ROM and re-create the failed file system by issuing the newfs command:

newfs /dev/rdsk/

is the name of the raw disk partition that contains the corrupted file system.

3. Check the new file system by using fsck:

fsck /dev/rdsk/

4. Mount the new file system on a temporary mount point:

mount /dev/dsk//mnt

5. Change to the /mnt directory:

cd /mnt

6. Write protect the tapes so that you don’t accidentally overwrite them.

7. Load the tape and issue the following command:

ufsrestore rf /dev/rmt/0

The entire content of the tape is restored to the file system. All permissions, ownerships, and dates remain as they were when the last incremental tape was created.

8. Verify that the file system is restored:

ls

9. Remove the restoresymtable file that is created and used by ufsrestore to checkpoint the restoration:

rm restoresymtable

10. Change to the root (/) directory:

cd /

11. Unmount the newly created file system:

umount /mnt

12. Check the new file system with fsck:

fsck /dev/rdsk/

The restored file system is checked for consistency.

13. If you are recovering the root (/) file system, create the boot blocks on the root partition by using the installboot command:

installboot /usr/platform/’uname-I’/lib/fs/ufs/bootblk\
/dev/rdsk/

The installboot command installs the boot blocks onto the boot disk. Without the boot blocks, the disk cannot boot.

14. Insert a new tape into the tape drive and back up the new file system:

ufsdump 0uf /dev/rmt/n /dev/rdsk/

A level 0 backup is performed. You should immediately make a backup of a newly created file system because ufsrestore repositions the files and changes the inode allocation.

15. Reboot the system with a reconfiguration reboot:

# shutdown -y -g0 -i0
ok boot -r

The system is rebooted.

Extra Notes on UFSrestore

When you restore files in a directory other than the root directory of the file system, ufsrestore re-creates the file hierarchy in the current directory. For example, if you restore to /home files that were backed up from /users/bcalkins/files, the files are restored in the directory /home/users/bcalkins/files.

When you restore individual files and directories, it’s a good idea to restore them to a temporary directory such as /var/tmp. After you verify that you’ve retrieved the correct files, you can move them to their proper locations. You can restore individual files and directories to their original locations; however, if you do so, you should be sure that you do not overwrite newer files with older versions from the backup tape.

You should not forget to make regular backups of your operating system. Losing all the customization you dosuch as adding user accounts, setting up printers, and installing application softwarewould be disastrous. Whenever you make modifications that affect the root (/),/usr, /opt, or other operating system directories, you should bring down the system into single-user mode and perform a level 0 dump.

you can edit the entries in the /etc/syslog.conf to direct to another file eg /var/log/syslog instead of /dev/console. After that, issue kill -HUP to “reinitialize” the config

or if you want to stop syslog process/daemon in Solaris 10, (not /etc/init.d/syslog stop)

it should be

svcadm disable svc:/system/system-log:default

svcadm disable svc:/system/system-log:default turned syslog off you need to also run svcadm enable svc:/system/system-log:default to turn it back on, after you made the right changes to /etc/syslog.conf so it does what you want. You can probably just comment out the line as it is also logged to file in /var/adm/messages.log

Turning syslog off is not a good idea.

That’s is How to Stop syslog Messages to Write Console on Solaris.

first time run this:

# /opt/SUNWexplo/bin/explorer -g

from then on, run this;

# /opt/SUNWexplo/bin/explorer

there are many options to explorer for certain things, but just by itself should get you most of what you need.

just want to repeat that for retention:

You can run /opt/SUNWexplo/bin/explorer. The first time you need to input some info (or just press enter). You’ll find the ouput in /opt/SUNWexplo/output.

Explorer download and installation:

http://docs.sun.com/app/docs/doc/819-6614/6n8k8pjc5?l=en&a=view

To be honest, this is the steps that really made me understood the steps and procedure and the concept behind the 10_Recommended patch for solaris kernel.

So, here it is:

Check Boot Disk

This step is to check which disks are the member of the boot mirror. We can say that this is the check disk mirror / disk membership step


# df -h /
Filesystem size used avail capacity Mounted on
/dev/md/dsk/d0 33G 7.3G 25G 23% /
#
# metastat -c d0
d0 m 33GB d10 d20
d10 s 33GB c1t0d0s0
d20 s 33GB c1t1d0s0

As you can see, there are two disk that comprise the boot mirror (d0), 33GB c1t0d0s0 and c1t1d0s0, which is named d10 and d20 respectively

Check which disk is booting up

In this step, we will determine which of the disk are the one being use as the boot default boot disk.

Usually it’s the default ‘disk’ or ‘disk0′, but there are times, very rare, that ‘disk1′ is set as the default boot disk.

To know which disk is the one that boot up the system, you can use the eeprom command in the system shell:


# eeprom boot-device
boot-device=disk0


In this case, it’s the most common disk that is used as the boot disk – disk0. That means, when can detach the other disk as backup just in case the patching screw up.

Check The Bootability of the Backup Disk

Prior to patching, check if the other disk is booting. This is a precaution. Just in case the patching went sour, we know that we can always revert to a good disk, revert to the previous good booting condition of the server.

Since from the previous step, we know that the default boot disk is ‘disk0′, we will switch to ‘disk1′ and try to reboot the server and see if it will come up.

Now, there are two ways to set the value of the ‘boot-device’ paramter of the server. You can either set it at the system shell, or through the Boot PROM, depending on where you are at the moment.

Now, set the default boot disk to ‘disk1′

eeprom boot-device=disk1

or

set boot-device=disk1

After setting it up, reboot the server:

init 0 then boot

or

init 6

If you’re successfull, you just booted on the ‘other half’ of the bootdisk.

Now, don’t forget to switch back to disk0 !!!

Next, (optional… can differ from company to company)

# untar the patch file
cd /var/tmp
rm -rf PatchDir
mkdir PatchDir
mv S10KernelUpdate4.0.tar.gz PatchDir
cd PatchDir
gunzip -c S10KernelUpdate4.0.tar.gz|tar xf -

Splitting the Mirror

The next steps are the meat of the procedure. This is the patching of the kernel itself.. But of course, after checking the boot disk – whether the both disks are good- it’s time to break the mirror and patch one disk.

sync;metadeatch

detach the backup disk

metadetach d0 d20

# mount the detached root file system to root and modify these

mount /dev/dsk/c1t1d0s0 /mnt

vi /mnt/etc/vfstab
vi /mnt/etc/system

Modifying vsfstab and /etc/system of the detached disk will make sure that if the patching fail, we can alyas boot up to the backup disk.

Start Patching

# go to single user mode
sync;sync;init 0

init -s

Rebooting with command: boot -s
Boot device: /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@0,0 File and args: -s
SunOS Release 5.10 Version Generic_141414-02 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.

… You then follow the ReadMe document that comes with the Patch here.

Once the patching is done, you’ll see the difference of the patch level of the kernel.

Boot device: disk0 File and args:
SunOS Release 5.10 Version Generic_142900-02 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.

Optional
=——————–
For more installation messages refer to the installation logfile:
/var/sadm/install_data/PMGT:_TLP-Set_Solaris_10_SOE_S10KernelUpdate4.1_A1_04_27_10

Use ‘/usr/bin/showrev -p’ or ‘/usr/sbin/patchadd -p’ to verify
installed patch-ids.
Refer to individual patch README files for more patch detail.
Rebooting the system is usually necessary after installation.
svc.startd: The system is coming down. Please wait.
svc.startd: 20 system services are now being stopped.

!!! Please read the logfile for any required action before rebooting !
————–

reboot:! for the bank, it’s automatic

If all is good, you can reattach the other disk

metattach d0 d20

And you’re done.

Special shell variables
There are some variables which are set internally by the shell and which are available to the user:

Name Description
——————————————————————————–
$1 – $9 these variables are the positional parameters.

$0 the name of the command currently being executed.

$# the number of positional arguments given to this
invocation of the shell.

$? the exit status of the last command executed is
given as a decimal string. When a command
completes successfully, it returns the exit status
of 0 (zero), otherwise it returns a non-zero exit
status.

$$ the process number of this shell – useful for
including in filenames, to make them unique.

$! the process id of the last command run in
the background.

$- the current options supplied to this invocation
of the shell.

$* a string containing all the arguments to the
shell, starting at $1.

$@ same as above, except when quoted.

Branching
if then fi
if [[ $value -eq 7 ]];then
print "$value is 7"
fi
or:

if [[ $value -eq 7 ]]
then
print "$value is 7"
fior:

if [[ $value -eq 7 ]];then print "$value is 7";fi

if then else fi
if [[ $name = "John" ]];then
print "Your welcome, ${name}."
else
print "Good bye, ${name}!"
fi

if then elif then else fi
if [[ $name = "John" ]];then
print "Your welcome, ${name}."
elif [[ $name = "Hanna" ]];then
print "Hello, ${name}, who are you?"
else
print "Good bye, ${name}!"
fi

case esac
case $var in
john|fred) print $invitation;;
martin) print $declination;;
*) print "Wrong name...";;
esac

——————————————————————————–

Looping Command Syntax for Scripts

while do done
while [[ $count -gt 0 ]];do
print "\$count is $count"
(( count -= 1 ))
done
until do done
until [[ $answer = "yes" ]];do
print -n "Please enter \"yes\": "
read answer
print ""
done
for var in list do done
for foo in $(ls);do
if [[ -d $foo ]];then
print "$foo is a directory"
else
print "$foo is not a directory"
fi
done
continue…break
One can skip the rest of a loop and directly go to the next iteration with: “continue”.

while read line
do
if [[ $line = *.gz ]];then
continue
else
print $line
fi
done
One can also prematurely leave a loop with: “break”.

while read line;do
if [[ $line = *!(.c) ]];then
break
else
print $line
fi
done

http://www.well.ox.ac.uk/~johnb/comp/unix/ksh.html

Removing accounts from predefine list:

#!/bin/ksh

done

Or course, the sleep there is just for aesthetic.. I want to see the screen

Summary: User instruction on how to setup public-key authentication.

In setting up the ssh public-key authentication between servers, local and remote, we have to generate the key pairs and transfer it to the remote/server.

Client Side

The publickey authentication method is enabled by the SSHtectia package by default. A functional ID’s key pair can be generated using the ‘generate_keys’ script (may be located in /export/opt/SSHtectia//util/ or depending on your installation). That script, ‘generate_keys’, is use to generate user key pairs: id_dsa_2048_a and id_dsa_2048_a.pub (default names) in the centralized key location:

/etc/opt/SSHtectia/keys/

The script also creates an ‘identification’ file in /etc/opt/SSHtectial/keys/ that contains the name of the private keys:

# more identification
# SSH Tectia private key
IdKey /etc/opt/SSHtectia/keys/%U/id_dsa_2048_a

# OpenSSH private key
IdKey /etc/opt/SSHtectia/keys/%U/id_dsa

Don’t forget to substitute the private key filename for ‘id_dsa_2048_a’ or ‘id_dsa’ if you are using a different naming convention. If several key pairs are used, list private keys on a separate lines.

Server Side

The publickey authentication method is enabled for functional IDs ONLY by the SSHtectia package (how do we know if an account is such?).

Copy the public key file (i.e. id_dsa_2048_a.pub) to the server, to the centralized key location. You can use sftp, copy paste or any other method to do this.

Also copy the ‘authorization’ file (created by the ‘generate_keys’ script) from the cliet to the server’s centralized key location.

Test the connection.. it should work.. It worked on mine.

getfacl is a file utility for viewing the access control list information associated with a file or directory.

For a memory aid, you can think of ‘getfacl’ as “Get File ACL“.. ACL being Access Control List.

Access control lists are extended attributes added to most major file systems in the 2.6 kernel to improve ability to control the access of files. They allow permissions to be set for individual groups and users and not just the owning user, owning group, and all other users.

setfacl is a command that allows you to set the Access Control List information for a file or directory.

Access control lists are extended attributes added to most major file systems in the 2.6 kernel to improve ability to control the access of files. They allow permissions to be set for individual groups and users and not just the owning user, owning group, and all other users.

You can read man pages for both getfacl and setfacl for more information.

getfacl and setfacl example….

Here’s an example of using the basic funtion of getfacl and setfacl

# getfacl

#setfacl

setfacl -m default:user::rwx,default:group::r-x,default:other:r-x,default:mask:rwx /u06/OneSource/datapump_dbdump

setfacl -m default:user:rcodapp1:r-x,default:group:r-x,default:other:—,default:mas:rwx /u06/OneSouce/datapump_dbdump

I want to post… say, borrowing, the content of that page to this post for my own personal reference… Love your own page right? And since I am more likely to open SysadminPH that cuddletech, I thought we not copy the Veritas tutorial page here for my ease of access?

The Cuddletech Veritas Cheat Sheet

by: B. Rockwood
benr@cuddletech.com

Overview:
——–

The purpose of this paper is to
quickly get you up to speed in Veritas,
and to act as a quick referance. All new
users to Veritas are HIGHLY encouraged to
first read the Veritas users guides enlucded
with Veritas, and found on docs.sun.com

Remember!: Almost all commands can use several
diffrent options that are similar
across all commands. The most used
of these is “-g ” which
specifies which Disk Group the command
will be executed on. For instance,
vxinfo will only display volume information
for volumes in the rootdg, to see
volumes in the datadg, for instance, use:
Ex: “vxinfo -g datadg”

———————————————–
DISPLAY and MONITORING
———————————————–

vxdisk list
List all disks used by Veritas (VX).

vxdisk list
Display detailed information about a
single disk, including mutlipathing
information, size, type, Vx version,
and more.

vxprint
Display report style information about
the current status of all Vx componants,
including disks, subdisks, plexes, and
volumes.

vxprint
Display report style information about
the current status of ONLY the componant
you request. So for instance,
“vxprint vol01″ shows information about
all subcomponants of vol01. This works
for plexes, disk groups, etc.

vxprint -hrt
Display detailed information about all
Vx componanats, including stwdith,
ncolumns, offsets, layout type, read-
policy, and more. This is best for
a true picture of your configuration.

vxdg list
Display listing and state information
of all Disk Groups.

vxdg list
Display detailed information about
a diskgroup, including flags, version,
logs status, etc.

vxinfo
Display volume status and volume type.
By default, only displays “rootdg”,
to display a diffrent Disk Group,
use “vxinfo -g “.

vxassist maxgrow
This command will output the maximum size
the volume specified can increased by,
specified in sectors.

————————————————–
DISK TASKS and COMMANDS
————————————————–

vxdiskadd
Adds a disk to Vx by Initializing and Encapsolating
it. Specified by its device name (ex: c0t1d0s2).
NOTE: You’ll need to reboot to finalize the
disk addition!

This command, can also be used to add a disk to
a specified disk group. Just follow the prompts.
No reboots needed for changing DG’s.

vxedit rename
Rename a Vx disk. Ex: “vxedit rename disk01 disk05″

vxedit set reserve=on
Sets the “reserve” flag to a Vx disk. This
is used to keep specific disks from being
accidentally, or generally used.

vxdisk offline
Used to “offline” a disk. The disk should
be removed from its diskgroup before being
offlined.

vxdisk rm
Used to remove disks from Vx control completely.
Ex: “vxdisk rm c0t1d0s2″ Make sure to
removed the disk from its diskgroup, and offline
the disk before removing it.

vxedit set spare=on
Sets the “spare” flag to a Vx disk. This is used
to make the specified disk a hot spare, which
is then added to the “hot spare pool”.

vxedit set spare=off
Same as above but removes the disk from the
“hot spare pool”.

—————————————————-
DISK GROUPS and COMMANDS
—————————————————-

vxdg init =
Creates a new disk group, and assigns the naming
scheme to the first disk added to the group.
ex: “vxdg init newdg newdg01=c0t10d0s2″.
NOTE: This is kinda tricky because the disk that
you’re adding can’t be a member of ANY DG, but
must be initialized. It’s easier to use
“vxdiskadd”, and add the disk to a newdg by
specifying a new DG name for the DG field.

vxdg deport
Disabled a diskgroup, but doesn’t remove it. Often
used as an organized pool of disk to realocate, and
to moved DG’s from one system to another.

vxdg import
Reverse of above. Enables local access to the specified
disk group.

vxdg -n Change a Disk Groups name.

vxdg list
Use this to check the version numbers of Disk
Groups. Shows other details about the DG too.

vxdg destroy
Removes the specified DG, and frees all its disks
back to general use by Vx.

-= Quick Chart!: Disk Group Version Number Translation

VxVM Introduced Supported
Release Version Versions
——- ———— ———
1.2 10 10
1.3 15 15
2.0 20 20
2.2 30 30
2.3 40 40
2.5 50 50
3.0 60 20-60

———————————————————–
SUBDISKS and COMMANDS
———————————————————–

vxmake sd ,,
Creates a subdisk with the specified name,
and by the offset and length specified.
ex: “vxmake sd disk02-01 disk02,0,8000″
NOTE: If you are going to add this subdisk
to a plex, its good to check the other
subdisks in that plex to see what their
lengths and offsets are, use the command:
“vxprint -st”

vxedit rm
Removes a subdisk.

vxsd assoc ,….
Associates the specified subdisks to
the specified plex. Example:
“vxsd assoc vol01-03 disk01-01,disk02-01″
NOTE: Striped volumes are diffrent,
you need to specify the column# so
use the following:

vxsd -l
assoc ,…
Same as above, but used for associating
subdisks to a striped plex. Use the command
“vxprint -st” to see what other subdisk
in the plex look like, and then set the
new subdisks column number and offset
(found in the seventh column of output)
to the appropriate value.

vxsd aslog
Adds a log subdisk to the specified plex.
Ex: “vxsd aslog vol01-02 disk03-01″

vxsd dis
Disassociates the specified subdisk from its
current plex.

——————————————————
PLEXS and COMMANDS
——————————————————

vxmake plex sd=,,….
Creates a new plex by the name specified and
assigns the specified subdisks to it.

vxmake plex layout= stwidth= ncolumn= sd=…
Like above command, but specifies layout type
as defined by , which is used for creation
of striped and RAID5 plexes. The layout is
constrained by the defined number of columns,
and stripe width. Subdisks specified are
added to the created plex.

vxplex att Associates specified plex with specified volume.
(Adds a mirror)
NOTE: Attachment will take a while. Watch
it with Vxtask, or via vxprint

vxplex dis Disassociate specified plex from its connected
volume.

vxedit -r rm Remove the plex.

vxmend off Offlines a plex for repair to it’s disks.

vxplex det Detaches specified plex from its connected
volume, but maintians association with it’s
volume. The plex is no longer used
for I/O untill it is (re)attached.

vxmend fix clean Used to clean plexes that are in the
“unclean” state. Used with unstartable
volumes.

vxplex mv
Moves the data content from the origonal
plex onto a new plex.
NOTE: The old plex must be active (ENABLED).
The new plex should be the same length, or
larger than the old plex. The new plex
must not be associated with another volume.
(duh)

vxplex cp
Copies the data from the specified volume
to a new plex.
NOTE: The new plex cannot be associated
with any other volume. The new plex,
further, will NOT be attached to
the specified volume. (Also, see notes
from above)

——————————————————-
VOLUMES and COMMANDS
——————————————————-

vxassist make
Creates a new volume with the name specified
and is made to the length specified.
Ex: “vxassist make newvol 10m”
NOTE: This command will pull disk space
from the generally avalible Vx disk space.

vxassist make layout= ….
Like the above command, but with layout specified.
The most common layouts are: striped and raid5
ex: “vxassist make newvol 100m layout=raid5 disk01 disk02 disk03″
NOTE: See the vxassist(1M) man page for more information.

vxmake vol len= plex= ,…
Creates a new volume of specified length (usually
in sectors), and attachs the specified plexes to that
volume. Useful for creating volumes to house
copied or moved plexes.
NOTE: See the vxmake(1M) man page for more information.

vxvol init [plexname]
Manually sets the state of a volume.
NOTE: Not for the squimish.

vxassist maxsize [layout=raid5]
Returns the maximum size avalible via Vx to create
a new volume. By adding “layout=raid5″ to the command
the calulations take into account losse due
to raid5. Output is in sectors and Megs.

vxassist maxgrow
Returns the maximum ammount of Vx space that
can be added to the specified volume.

vxassist mirror
Creates a mirror for the specified volume.
NOTE: Think of this as “handsfree plex creation”.
This is fast, but the disks you want used
may not be used… often best to do manually.

vxassist addlog
Adds a Dirty Region Log (DRL) for the specified volume.

vxassist remove log
Reverse of above.

vxvol start
Starts a volume

vxvol stop
Stops a volume. Alternately you can use command as
such: “vxvol stopall” in order to stop all volumes.

vxassit growto/growby/shrinkto/shrinkby
Resizes the volume specified. Use one of the
following: growto, growby, shrinkto, and shrinkby
in order to descide what specifies.
By default length is specified in sectors.
This does not resize the filesystem inside the volume.
NOTE: Don’t shrink volumes to be less that
its contained filesystem! (duh)

vxvol set len=
An alternate to above command. Sets the absolute
lenths of the specified volume to the length
specified, by default, in sectors. This
does not resize the filesystem inside the volume.

NOTE: There is also a resize(1M) command, used
for resizing both volume AND filesytem. See
the man page for that one.

vxedit rm
Removes the specified volume. (poof!)
NOTE: If the volume specified is in the ENABLED
state, you will need to use the command
“vxedit -f “. Also, using the “r”
with “f” will remove all plexes and subdisks
with the volume. If you didn’t guess, “r”
is Recursive, and “f” is Force.

—————————————————————-
Misc Stuff:

To calculate the size of a filesystem inside a volume, use
the command:
fstyp -v | head -30 | grep ncg
Ignore the errors. Output will look this this:
# fstyp -v /dev/vx/rdsk/datadg/vol01 | head -30 | grep ncg
ncg 17152 size 70254592 blocks 65863396
# Broken Pipe
Unknown_fstyp (no matches)
The size found after the label “size” is presented in kilobytes.
You can convert to sectors by multiplying by 2.

———–

To calculate the size of a volume, use vxprint, and look for the
“len”. The volume length is in sectors. Convert to kilobytes
by dividing by 2.

————-

Volume Growth Procudure:
1) You can use vxassist to estimate the max size of
a given volume based on the disks you wish to add:
ex: # vxassist -g rootdg maxgrow vol01 disk01 disk02 disk03

2) Next, actually grow the volume (NOT THE FS) via the
command (assuming maxgrow outputed 10639360 as the maxsize):
ex:# vxassist -g rootdg growto vol01 10639360 disk01 disk02 disk03

3) Now VxVM grinds away, monitor with vxtask.

4) Now Grow the Filesystem, for UFS use:
# /usr/lib/fs/ufs/mkfs -F ufs -M /export /dev/vx/rdsk/rootdg/vol01 10639360

for VXFS ufs:
# /usr/lib/fs/vxfs/fsadm -b 10639360 -r /dev/vx/rdsk/rootdg/vol01 /mnt
—————————————————————

5) Done!

———-

Changing User/Group of a Raw Volume: (ex:)
vxedit -g xxxdg set group=dba data_vol_123
vxedit -g xxxdg set user=oracle data_vol_123

Thanks to Ben Rockwood! Cheers!

[root@localhost] /work/users> metastat -c d103
d103 p 32GB d100
d100 m 68GB d101 d102
d101 s 68GB c1t2d0s0
d102 s 68GB c1t3d0s0

[root@localhost] /work/users> metastat -p d103
d103 -p d100 -o 32 -b 58720256 -o 127926432 -b 8388608
d100 -m d101 d102 1
d101 1 1 c1t2d0s0
d102 1 1 c1t3d0s0

So from the first metastat -c d103.. that’s a mirrored 68G partition, d100 and a 32G soft partition d103.. We still have around 35G of space.

update: — someone comment please.. this information is incomplete!

Got a page.. something like “Fault found by metastat” in short description in Remedy…

# metastat | grep Need
State: Needs maintenance
State: Needs maintenance

Which disk?

# metastat d9
d9: Mirror
Submirror 0: d19
State: Needs maintenance
Submirror 1: d29
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 134221440 blocks (64 GB)

Device Relocation Information:
Device Reloc Device ID
c0t2d0 Yes id1,sd@SSEAGATE_ST373307LSUN72G_3HZ6Y1EN000074312CVW
c0t3d0 Yes id1,sd@SSEAGATE_ST373307LSUN72G_3HZ6Y46Y0000743249BK


Check for hard errors to verify if this disk can really be replaced… if it passed (on your criteria), you can try re-syncing it…

c# metareplace -e d9 c0t2d0s5
d9: device c0t2d0s5 is enabled

Verify that it’s doing what it is expected..

# metastat d9
d9: Mirror
Submirror 0: d19
State: Resyncing
Submirror 1: d29
State: Okay
Resync in progress: 0 % done
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 134221440 blocks (64 GB)

And we wait…..