|
|
Bug in SVM or just bad device path?
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
342 Views
(page loaded in 0.023 seconds)
Similiar Articles: Bug in SVM or just bad device path? - comp.unix.solarisPanic on ZFS import - comp.unix.solaris... spot > many corruptions, and will just ... night, ZFS decided that the RAID had gone bad and since it was the only device ... metadb problem - comp.unix.solarisBug in SVM or just bad device path? - comp.unix.solaris I have a software raid 5 partition that has a problem with relocation information ... d10 d10 s 11GB c1t0d0s0 d20 s ... problem with mirrored root - comp.unix.solarisBug in SVM or just bad device path? - comp.unix.solaris problem with mirrored root - comp.unix.solaris... problem with S10 1009 and seting up a mirrored root device ... tar truncates end of file name - comp.unix.solarisWhat is the path length of the file in ... the possible cause? >> >I would just use GNU tar (gtar) instead. It is a really bad ... to the end of an ... default device listed ... USB as standard debug interface - comp.arch.embeddedThe bug (feature?!) hits if the serial->USB ... chattering away when Windows examines the device. In development we can just ... code path is not taken or until a code path ... VXVM, active detached volume?!! - comp.unix.solarisHowever, it bugs me. Is ... mode=UNKNOWN recov_id=0 device: minor=121000 bdev=269/121000 cdev=269/121000 path ... imagine that paths are bad. I presume that this is just ... access control and pool servers - comp.protocols.time.ntp ...I think I solved this just before hitting "send". ... Could we have encountered a subtle ntpd bug here? ... br> <br> This doesn't say or imply that it's a bad ... [comp.publish.cdrom] CD-Recordable FAQ, Part 1/4 - comp.publish ...Archive-name: cdrom/cd-recordable/part1 Posting-Frequency: monthly Last-modified: 2008/10/09 Version: 2.71 Send corrections and updates to And... T1000/T2000 + ZFS + SAS performance - comp.unix.solaris... but we don't want to lose data or have a bad ... RPM cf 10k or 15k) but for me, zfs (or even svm ... Maybe it's a write-only device :-O Apparently, a bug in the mpt driver. Please help: Latest Sunfire v20Z bios, etc. - comp.unix.solaris ...Sorry, but I feel BIOS updates and device drivers should ... The bad part is their amount of DEPENDENCE on community ... I'll bet anything the Solaris path down the road will ... Bug in SVM or just bad device path? - Database Support @ dbaspot ...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 ... Bug in SVM or just bad device path? - comp.unix.solaris | Computer ...Panic on ZFS import - comp.unix.solaris... spot > many corruptions, and will just ... night, ZFS decided that the RAID had gone bad and since it was the only device ... 7/23/2012 10:34:23 AM
|
|
|
|
|
|
|
|
|