no devices found as I've clean already the dead IO path.
basically what I did it:
# vxvol -g dg stopall
# vxdg destroy
# vxdisk rm disk
# unbind the LUN
#powermt check force
# devfsadm -C -v
# vxdctl enable;vxconfigd -k
most of these phantom disk aren't part of the dg I've just destroy but
I
This seems to be the right track but we may not have gone far enough. By
this I mean I went to sort.symantec.con and searched on the error code
V-5-1-8645. I got two hits. I selected the second,
www.symantec.com/docs/TECH61541 because it referenced a tech note. The note
is about Netbackup but,
...@gmail.com
Subject: [Veritas-vx] Ghost VXVM Devices
To: veritas-vx@mailman.eng.auburn.edu
Message-ID:
cal0mbks-azjigw7_shw_v5jyuetkagiqaebszdr0d1keqhc...@mail.gmail.com
Content-Type: text/plain; charset=ISO-8859-1
Hi All,
I need some help tips on this, basically I don't know the exact
history
On Wed, Aug 17, 2011 at 10:13 PM, William Havey bbha...@gmail.com wrote:
This seems to be the right track but we may not have gone far enough. By
this I mean I went to sort.symantec.con and searched on the error code
V-5-1-8645. I got two hits. I selected the second,
Hi All,
I need some help tips on this, basically I don't know the exact
history of this server but I just destroy the last DG and remove the
disk that is part of that DG on the VXVM control.
I did:
# vxvol -g dg_name stopall
# vxdg destroy dg_name
# vxdisk rm disk_name
# unbind the LUN(EMC)
#
Hi Bill,
After doing what you've suggested(edited the file), I encountered this
error during the vxconfigd -k.
root@sv3# vxconfigd -k
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming
/dev/rdsk/c2t5006016039A0222Ed5s2 by NR list: I/O error
VxVM vxconfigd ERROR V-5-1-8645 Error in claiming