cancel
Showing results for 
Search instead for 
Did you mean: 

I/O error occured on Path c2t0d0s2 belonging to Dmpnode c4t0d0s2, when using vxdiskunsetup

luis_carlos_rub
Level 2
I wanted to remove a mirror of two disk, c2t0d0, and c4t0d0.

After removing the plex and the disk this was the status:

# vxprint -g ogw1dg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
dg ogw1dg ogw1dg - - - - - -

dm ogw1dgc2t0d0 c4t0d0s2 - 142831616 - - - -

v vol01 fsgen ENABLED 142831616 - ACTIVE - -
pl vol01-01 vol01 ENABLED 142831616 - ACTIVE - -
sd ogw1dgc2t0d0-01 vol01-01 ENABLED 142831616 0 - - -
#

when unsetupping c2t0d0
# /etc/vx/bin/vxdiskunsetup -C c2t0d0

First error was:
Jun 11 00:46:00 OGW2 vxio: WARNING: VxVM vxio V-5-0-2 Subdisk ogw1dgc2t0d0-01 block 196608: Uncorrectable write error

I also found this error in dmpevents.log, for dynamic multipathing
root@OGW2:/etc/vx/log# head dmpevents.log
------LOGGING START------------LOGGING START------
Thu Jun 11 00:46:00.167: I/O error occured on Path c2t0d0s2 belonging to Dmpnode c4t0d0s2
Thu Jun 11 00:46:00.172: I/O analysis done on Path c2t0d0s2 belonging to Dmpnode c4t0d0s2

Is it possible that Veritas was accessing to c4t0d0 trought c2t0d0???. According to "vxdisk list c4t0d0" there is only one path defined and it is c2t0d0. So when c2t0d0 was unsetupped, Veritas could not reach c4t0d0???

root@OGW2:/# vxdisk list c4t0d0
Device: c4t0d0s2
devicetag: c4t0d0
type: auto
hostid: OGW1
disk: name= id=1244812456.121.OGW2
group: name=ogw1dg id=1244812625.127.OGW2
info: format=cdsdisk,privoffset=256,pubslice=2,privslice=2
flags: online ready private autoconfig noautoimport
pubpaths: block=/dev/vx/dmp/c4t0d0s2 char=/dev/vx/rdmp/c4t0d0s2
version: 3.1
iosize: min=512 (bytes) max=2048 (blocks)
public: slice=2 offset=2304 len=142837504 disk_offset=0
private: slice=2 offset=256 len=2048 disk_offset=0
update: time=1245065729 seqno=0.47
ssb: actual_seqno=0.0
headers: 0 240
configs: count=1 len=1280
logs: count=1 len=192
Defined regions:
config priv 000048-000239[000192]: copy=01 offset=000000 enabled
config priv 000256-001343[001088]: copy=01 offset=000192 enabled
log priv 001344-001535[000192]: copy=01 offset=000000 enabled
lockrgn priv 001536-001679[000144]: part=00 offset=000000
Multipathing information:
numpaths: 1
c2t0d0s2 state=enabled

root@OGW2:/#
1 REPLY 1

Gaurav_S
Moderator
Moderator
   VIP    Certified
Hello,

I guess point of confusion is names.... If we see above on "vxdisk list c4t0d0s2" output , c4t0 is a DMP node name while c2t0 is a OS name..... similary if you do vxdisk list on c2t0 (DMP name) what does it reports ?

best is to check "vxdisk -e list" to match the correct disk names..

Anyways coming back to original query.... actual issue is disk physically having errors... you should have got some SCSI errors in the messages file... should be checked with hardware vendor...


Gaurav