Bug in SVM or just bad device path?

  • Follow


Hello All.
I have a software raid 5 partition that has a problem with relocation
information:

  # metadevadm -r -v
  Invalid device relocation information detected in Solaris Volume
Manager
  Please check the status of the following disk(s):
 
c1t13d0

I've replaced c1t13d0 and used metareplace to add the new disk in and
the array is resyncing. Still getting that error above though.  The
man page for metadevadm says this is
due to it being an invalid device name.

The man pages says to use metadevadm -u <device> to update the
relocation info but
this gives an odd error:

  # metadevadm -u c1t13d0
  metadevadm: temp.au.com: No such file or directory

What the heck is going on here?  metatstast is able to read the
relocation info, why is metadevadm giving the error?

  # metastat
  ...
  Device Relocation Information:
  Device    Reloc Device ID
  c1t1d0    Yes   id1,ssd@n20000004cf8325c9
  c1t0d0    Yes   id1,ssd@n20000004cf83051b
  c1t3d0    Yes   id1,ssd@n2000002037c63915
  c1t4d0    Yes   id1,ssd@n20000004cf831edd
  c1t5d0    Yes   id1,ssd@n20000004cf20ad38
  c1t8d0    Yes   id1,ssd@n20000004cf7fff8e
  c1t9d0    Yes   id1,ssd@n20000004cf9612d7
  c1t10d0   Yes   id1,ssd@n20000004cf83217b
  c1t11d0   Yes   id1,ssd@n20000004cf8325b5
  c1t12d0   Yes   id1,ssd@n20000004cf831677
  c1t13d0   Yes   id1,ssd@n200000203784120c

some extra info...
# metastat -c
d71              p  150GB d69
d70              p   60GB d69
    d69          r  271GB c1t3d0s0 c1t4d0s0 c1t5d0s0 c1t8d0s0 c1t9d0s0
c1t10d0s0 c1t11d0s0 c1t12d0s0 c1t13d0s0 (resyncing)
d1               m   15GB d11 d21
    d11          s   15GB c1t0d0s1
    d21          s   15GB c1t1d0s1
d7               m  2.6GB d17 d27
    d17          s  2.6GB c1t0d0s7
    d27          s  2.6GB c1t1d0s7
d4               m  3.9GB d14 d24
    d14          s  3.9GB c1t0d0s4
    d24          s  3.9GB c1t1d0s4
d0               m   11GB d10
    d10          s   11GB c1t0d0s0
d20              s   11GB c1t1d0s0


# metadb
        flags           first blk       block count
     a m  p  luo        16              8192            /dev/dsk/
c1t0d0s3
     a    p  luo        16              8192            /dev/dsk/
c1t0d0s5
     a    p  luo        16              8192            /dev/dsk/
c1t0d0s6
     a    p  luo        16              8192            /dev/dsk/
c1t1d0s3
     a    p  luo        16              8192            /dev/dsk/
c1t1d0s5
     a    p  luo        16              8192            /dev/dsk/
c1t1d0s6
     a    p  luo        16              8192            /dev/dsk/
c1t2d0s3
     a    p  luo        16              8192            /dev/dsk/
c1t2d0s5
     a    p  luo        16              8192            /dev/dsk/
c1t2d0s6

Thanks
0
Reply bl8n8r 5/27/2008 3:34:45 PM


0 Replies
341 Views

(page loaded in 0.034 seconds)

Similiar Articles:













7/23/2012 10:34:23 AM


Reply: