- 论坛徽章:
- 7
|
That day I have dealed with one case about vxvm disk group.
First of all, I tried to import oradg.
# vxdg import oradg
VxVM vxdg ERROR V-5-1-587 Disk group oradg: import failed: Disk is in use by another host
But there are no any servers including oradg imported.
Then, I tried to import oradg forcedly
# vxdg -f -C import oradg
VxVM vxdg ERROR V-5-1-587 Disk group oradg: import failed: Serial Split Brain detected. Run vxsplitlines
Now I think why the disk group can not be imported anyway?
I start to talk with the Field engineer, and discuss the server process recently. I found out some disk error happend to the exact oradg!
I searched one relavant document from support.veritas.com, and followed by the instruction of the articles. But I could not resovle it!
Here we should backup the disk group private slice information
# vxprivutil dumpconfig /dev/rdsk/c3t4d6s3 >/var/tmp/c4t4d6s3.bak
run explorer to collect all system configuaration, messages and so on.
Now only I can do is remove the suspective disks from oradg
# vxdisk offline c4t5d6
(some same commands ignored)
Import oradg again. Well done!
# vxdg import oradg
Now remove the defective disks
# vxdg -g oradg -k rmdisk c4t5d6
(some same commands ignored)
re-initialized the disks
vxdiskunsetup -C c4t5d6
vxdisksetup -i c4t5d6 format=sliced
# vxdg -g oradg -k adddisk oradg04=c4t5d6
# vxrecover -g oradg -sb
The end.
From the phenomenon, It maybe a VxVM 4.0 bug in my viewpoint. But not sure this
![]()
The following docs is contributed by Symantic Corp.
Refer to
http://support.veritas.com/docs/269233
本文来自ChinaUnix博客,如果查看原文请点:http://blog.chinaunix.net/u/43/showart_122528.html |
|