original source: http://www.knodel.net/jeff/blog
Filesystems in shared disk group will not mount shared:
Tuesday, July 25th, 2006Problem: You have imported your CVM disk group as shared, and its imported on all nodes of your cluster, but when you try to mount a volume, you get:
# mount -F vxfs -o cluster /dev/vx/dsk/oratestdg/oratest /oratest
UX:vxfs mount: ERROR: V-3-20003: Cannot open /dev/vx/dsk/oratestdg/oratest: No such device or address
UX:vxfs mount: ERROR: V-3-24996: Unable to get disk layout version
Solution: The problem is that you do not have the disk group activation mode set properly. If you run a vxdg list [dgname] , you can see the activation mode for each node.
Examine the contents of your /etc/default/vxdg. You will probably see a line like:
default_activation_mode=off
Change it to default_activation_mode=sw, and restart veritas.
If you want to do it interactively by disk group, try vxdg -g [dgname] set activation=sw
Cannot add device to a CDS Disk Group
Monday, July 3rd, 2006Problem: You are trying to initialize a disk group, and you are getting the following error:
# vxdg init vxfencoorddg c2t0d64
VxVM vxdg ERROR V-5-1-6478 Device c2t0d64s2 cannot be added to a CDS disk group
Solution: Set up the disk to be a CDS disk before running the init.
# vxdisksetup -i c2t0d64 format=cdsdisk
# vxdg init vxfencoorddg c2t0d64
VERITAS vxfentsthdw will not process i/o fencing quorum disks
Monday, July 3rd, 2006Problem: You are trying to run veritas’s hardware test, and despite meeting the hardware requirements, the tests fail with:
VCS FEN vxfenadm ERROR V-11-2-1204 Command 3 FAILED for: /dev/vx/rdmp/c2t0d215s2
VCS FEN vxfenadm ERROR V-11-2-1210 CLEAR failed for: /dev/vx/rdmp/c2t0d215s2
VCS FEN vxfenadm ERROR V-11-2-1133 Error returned
Solution: Veritas’ tool cannot use the Veritas Dynamic Multipathing device entry; you cannot use the /dev/rdmp path to the disks. Try using the first /dev/rdsk/CTDS path to the device available.
While I am at it — if you are using the raw disk path (ie /dev/rdsk…) and it says that the device does not exist, and an ls -l (path) shows that it does — you need to write a solaris label onto the disk before the veritas processes can use the disk.
Sample Error: “Disk /dev/rdsk/c3t0d219s2 is not existent on host hostname”
# format c#t#d#; vxdctl enable
Reattach Failed or Failing disks in Veritas
Monday, June 26th, 2006Problem: A temporary problem caused veritas to label your disks as “Failed” or “Failing”:
Solution for Failed: vxreattach
Solution for Failing: vxedit -g set failing=false
Veritas Plexes show “DISABLED RECOVER” in status
Monday, June 26th, 2006Problem: The vxprint output shows that the plexes for the volume are in “DISABLED RECOVER” state.
Solution:
The following commands must be run on a plex to change the state of the plex to “CLEAN”. The volume can then be started, but a fsck may be required before mounting the file system.# vxmend -o force off
# vxmend on
# vxmend fix clean
# vxvol start
# fsck -F vxfs /dev/vx/rdsk//
# mount -F vxfs /dev/vx/dsk// /mountpoint
No comments:
Post a Comment