1. Unable to import diskgroup:
Their may be many reasons for which you may not be able to import the diskgroup however the diskgroup shows clean in vxdisk -o alldgs list
One common reason is the diskgroup was not deported cleanly . Use the below commands to fix the issue
#vxdg -f -C import appdg -- which will clean up the existing host id and import the diskgroup
2. A quick way to check which are the volumes in a diskgroup have been started
#vxinfo -g
# vxinfo -g datadg
datavol fsgen Startable
In the above output, the last field "startable" means volume is fine can be started by the following commands
# vxvol -g datadg start datavol
# vxinfo -g datadg
datavol fsgen Started
#
Using vxprint also you can also get the status of the volumes
#vxprint -qhtg
Below steps are used for SAN migration. Its very simple.
Attaching a plex:
# vxplex -g appdg att appvol appvol-01
Removing a plex:
-- If above looks good, then go ahead & detach old plex
# vxmend -g testdg off oradata9-01
# vxplex -g testdg dis oradata9-01
remove the plex
# vxedit -g -rf rm --- delete the plex
remove the disk from diskgroup
# vxdg -g appdg rmdisk disk01
Forcibly starting a disabled volume:
# vxvol -g mydg -o bg -f start myvol
Clearing the failing flag on a disk
Failing flag could be because of many reasons such as intermittent I/O error which could be because of temporary removal of a cable, controller fault, partially faulty LUN in the array.
#vxedit set failing=off mydg02
datavol fsgen Startable
# vxinfo -g datadg
datavol fsgen Started
#
Using vxprint also you can also get the status of the volumes
# vxplex -g appdg att appvol appvol-01
Removing a plex:
-- If above looks good, then go ahead & detach old plex
# vxmend -g testdg off oradata9-01
# vxplex -g testdg dis oradata9-01
remove the plex
# vxedit -g
remove the disk from diskgroup
# vxdg -g appdg rmdisk disk01
No comments:
Post a Comment