Solaris 10 Volume Manager - adding slice to metadb

UNIX Solaris
1

Hi all,

I added a new disk slice to the current metadb.
Below is what I see

bash-3.2# metadb -i
        flags           first blk       block count
     a m  p  luo        16              8192            /dev/dsk/c0t0d0s7
     a    p  luo        8208            8192            /dev/dsk/c0t0d0s7
     a    p  luo        16400           8192            /dev/dsk/c0t0d0s7
     a    p  luo        16              8192            /dev/dsk/c0t1d0s7
     a    p  luo        8208            8192            /dev/dsk/c0t1d0s7
     a    p  luo        16400           8192            /dev/dsk/c0t1d0s7
     a        u         16              8192            /dev/dsk/c0t2d0s7
     a        u         8208            8192            /dev/dsk/c0t2d0s7
     a        u         16400           8192            /dev/dsk/c0t2d0s7

I am missing the following flags.

p - replica's location was patched in kernel
l - locator for this replica was read successfully
o - replica active prior to last mddb configuration change

q1) Can anyone elaborate the meaning of 'p' and 'l' especially ?

q2) How do make the flags appear ?

Regards,
Noob

2

These flags get added during next boot. As long as you see "u" flag for the new disk and no "UPPERCASE" flags (ie. WMDFSRB) present you are good with SVM.

Just ensure the

metadevadm -u <cXtXdX>

command executed after any disk change with the replaced device name. This command update the device relocation information. You can check this by running

metastat

and look for the last few lines of output

3

Hi rinjohn,

Thanks for your reply. If I have done the following

1) remove the metadevice of the old disk/slice
2) remove the slice of old disk from metadb
3) replace old disk with new disk
4) add the slice of the new disk to metadb
5) recreate a metadevice

Do I still need to issue metadevadm ? -- thought when I add the new slice to metadb , the deviceID will be added automatically ?

Regards,
Noob

4

You can verify the output of #metastat and if the new disk ID id missing, run #metadevadm command.

Sample

Device Relocation Information:
Device              Reloc       Device ID
c1t2d0              Yes         id1,sd@SSEAGATE_ST39204LCSUN9.0G3BV0N1S200002103AF29
c2t2d0              Yes         id1,sd@SSEAGATE_ST39204LCSUN9.0G3BV0P64Z00002105Q6J7
c1t1d0              Yes         id1,sd@SSEAGATE_ST39204LCSUN9.0G3BV0N1EM00002104NP2J
c2t1d0              Yes         id1,sd@SSEAGATE_ST39204LCSUN9.0G3BV0N93J000071040L3S
c0t0d0              Yes         id1,dad@s53554e575f4154415f5f53543339313430412525415933

If this is not updated then SVM fail to understand disk change and probably you may receive the below message in subsequent reboot.

[ID 209699 daemon.error] Invalid device relocation information detected in Solaris Volume Manager