Sponsored Content
Operating Systems Solaris Cannot mount Veritas volumes after cluster patch. Post 302587599 by buggin on Thursday 5th of January 2012 10:10:43 AM
Old 01-05-2012
Cannot mount Veritas volumes after cluster patch.

I am working with a Sun StoredgeTek 6540 disk array connected to two Sun 490 servers. After taking one of the 490 nodes on the cluster down to single user mode I proceeded to install the latest cluster patch from Oracle. After the patch was completed the system rebooted, failed to rejoin the cluster, crashdumped and rebooted continuously. The second node which was not updated and was functioning fine beforehand is also no longer able to connect to all the drives or the main Veritas drive group. I was running Solaris 10 137137-09 Sun Cluster 3.2 and Veritas 5 on both 490s before the cluster patch. I have since removed all the patches from the cluster patch and now both systems can boot up and join the cluster but cannot access the main Veritas drive group.

I have tried vxconfigrestore which fails.

Here are some sample errors when booting:

Dec 22 10:59:22 server02 Cluster.Framework: stderr: VxVM vxdg WARNING V-5-1-560
Dec 22 10:59:22 server02 Cluster.Framework: stderr: Disk satadg08: Not found, last known location: FLEXLINE0_4
Dec 22 10:59:22 server02 VxVM vxdg WARNING V-5-1-560 Disk satadg31: Not found, last known location: FLEXLINE0_0
Dec 22 10:59:22 server02 VxVM vxdg WARNING V-5-1-560 Disk satadg10: Not found, last known location: FLEXLINE0_10
..............
Dec 22 10:55:35 server02 scsi: WARNING: /scsi_vhci/ssd@g500000e014adbd30 (ssd2):
Dec 22 10:55:35 server02 drive offline
Dec 22 10:56:18 server02 vxvm:vxconfigd: V-5-1-8646 Error in claiming /dev/rdsk/c6t600A0B8000470CC2000008A347E0DDD6d0s2: I/O error
Dec 22 10:56:18 server02 vxvm:vxconfigd: V-5-1-8646 Error in claiming /dev/rdsk/c6t600A0B80004702300000085147E0E215d0s2: I/O error
Dec 22 10:56:18 server02 vxvm:vxconfigd: V-5-1-8646 Error in claiming /dev/rdsk/c6t600A0B80004702300000082147E0D921d0s2: I/O error
..........

I have copies of vxprint and vxdisk output from when the system was functioning normally and have 3 months worth of full tape backups but do not know where to begin to try and restore the main disk group. Been doing tons of reading online and just cannot seem to find the identical situation to mine. Not yet familiar enough with Veritas and Sun Cluster to fix this but am trying to learn as much as possible from this experience before this server is later put into production.
 

8 More Discussions You Might Find Interesting

1. High Performance Computing

veritas cluster with kernel patch update

hi all, can someone please share their process on how to kernel patch a red hat ent 4 with veritas cluster 5? it's compose of a primary and backup node. the resources are db, disk, nic. it doesn't need to be detail, just give me the steps like: login to the backup node and update the... (0 Replies)
Discussion started by: itik
0 Replies

2. Linux

one nfs mount point for many logical volumes

hi i am wondering if it is possible to use one nfs mount point for several logical volumes. i have a top level directory /imaging with data1 - data50 below it. each dataX directory is a logical volume configured through LVM. if i mount them separately on the client (i.e. 50 lines in fstab... (1 Reply)
Discussion started by: user23
1 Replies

3. High Performance Computing

SUN Cluster Vs Veritas Cluster

Dear All, Can anyone explain about Pros and Cons of SUN and Veritas Cluster ? Any comparison chart is highly appreciated. Regards, RAA (4 Replies)
Discussion started by: RAA
4 Replies

4. UNIX for Dummies Questions & Answers

Move veritas filesystem space between Logical volumes

I have a veritas file system (fsA) that is nearing capacity. We have secondary file system (fsB). that is unused and would like to move some of it's disk space but I'm unsure as to how to do this with. /dev/vx/dsk/vg05/lvol05 25288704 21887258 3188911 88% ... (2 Replies)
Discussion started by: Steelysteel
2 Replies

5. OS X (Apple)

Mount a disk elsewhere /Volumes

When a new disk is connected to a Mac/OSX, it automatically mounts on /Volumes. Is it possible to manually mount it elsewhere? For example, on "/raid"? - m66 - (5 Replies)
Discussion started by: makrell66
5 Replies

6. Solaris

Veritas Cluster

How to create your cluster members routes and manual nat, and proxy. (2 Replies)
Discussion started by: padmaja@tech
2 Replies

7. Solaris

Sun cluster and Veritas cluster question.

Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC. Am thinking how to migrate to sun cluster setup instead. My plan as follows leave the existing vcs intact as a fallback plan. Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies

8. UNIX for Beginners Questions & Answers

How to extend a disk in veritas volume manager in veritas cluster?

Hi Experts, I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system. #hastatus -sum -- System State Frozen A node1 running 0 A node2 running 0 -- Group State -- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies
clvxvm(1CL)						 Sun Cluster Maintenance Commands					       clvxvm(1CL)

NAME
clvxvm - configure VERITAS Volume Manager for Sun Cluster SYNOPSIS
/usr/cluster/bin/clvxvm -V /usr/cluster/bin/clvxvm [subcommand] -? /usr/cluster/bin/clvxvm subcommand -v /usr/cluster/bin/clvxvm encapsulate /usr/cluster/bin/clvxvm initialize DESCRIPTION
The clvxvm utility initializes VERITAS Volume Manager (VxVM) on a Sun Cluster node and optionally performs root-disk encapsulation. There is no short form of this command name. You can only use this utility with VxVM versions 4.1 or later. For older versions of VxVM, instead use the scvxinstall(1M) utility. The general form of this command is as follows: clvxvm [subcommand] [options] You can omit subcommand only if options specifies the -? option or the -V option. Each option of this command has a long form and a short form. Both forms of each option are given with the description of the option in the OPTIONS section of this man page. You can only use this command from a node that is booted in cluster mode. All nodes in the cluster configuration must be current cluster members. All nodes must be added to the node authentication list. You can use this command only in the global zone. SUBCOMMANDS
The following subcommands are supported: encapsulate Encapsulates the root disk and performs other Sun Cluster-specific tasks. The encapsulate subcommand performs the following tasks: o Verifies that the current node is booted in cluster mode and that all other cluster nodes are running in cluster mode. o Verifies that the user is superuser. o Enforces a cluster-wide value for the vxio major number by modifying the node's /etc/name_to_major file, if necessary. This task ensures that the vxio number is the same on all cluster nodes. o Runs several VxVM commands to prepare for root-disk encapsulation. o Modifies the global-devices entry in the /etc/vfstab file that is specified for the /global/.devices/node@n file system, where n is the node ID number. The clvxvm utility replaces the existing device path /dev/did/{r}dsk with /dev/{r}dsk. This change ensures that VxVM recognizes that the global-devices file system resides on the root disk. o Twice reboots each node that is running clvxvm. The first reboot allows VxVM to complete the encapsulation process. The sec- ond reboot resumes normal operation. The clvxvm utility includes a synchronization mechanism to ensure that the utility reboots only one node at a time, to prevent loss of quorum. o Unmounts the global-devices file system. The file system is automatically remounted after the encapsulation process is com- plete. o Recreates the special files for the root-disk volumes with a unique minor number on each node. This subcommand expects that VxVM packages and licenses are already installed and that the VxVM configuration daemon is successfully enabled on this node. Each root disk that you encapsulate must have at least two free (unassigned) partitions. Users other than superuser require solaris.cluster.modify RBAC authorization to use this subcommand. initialize Initializes VxVM and performs other Sun Cluster-specific tasks. The initialize subcommand performs the following tasks: o Verifies that the current node is booted in cluster mode and that all other cluster nodes are running in cluster mode. o Verifies that the user is superuser. o Enforces a cluster-wide value for the vxio major number by modifying the node's /etc/name_to_major file, if necessary. This task ensures that the vxio number is the same on all cluster nodes. o Instructs the user to reboot the node to resume operation with the new vxio major number in effect, in case the number had to be changed. This subcommand expects that VxVM packages and licenses are already installed and that the VxVM configuration daemon is successfully enabled on this node. Users other than superuser require solaris.cluster.modify RBAC authorization to use this subcommand. OPTIONS
The following options are supported: -? ---help Displays help information. You can use this option either alone or with a subcommand. o If you use this option alone, the list of available subcommands is printed. o If you use this option with a subcommand, the usage options for that subcommand are printed. When you use this option, no other processing is performed. -V ---version Displays the version of the command. Do not specify this option with subcommands, operands, or other options. The subcommands, operands, or other options are ignored. The -V option only displays the version of the command. No other operations are performed. -v ---verbose Displays verbose information to standard output. You can use this option with any form of the command. OPERANDS
No form of this command accepts an operand. EXIT STATUS
The complete set of exit status codes for all commands in this command set are listed on the Intro(1CL) man page. This command returns the following exit status codes: 0 CL_NOERR No error 1 CL_ENOMEM Not enough swap space 3 CL_EINVAL Invalid argument 6 CL_EACCESS Permission denied 35 CL_EIO I/O error EXAMPLES
Example 1 Initializing VxVM on a Cluster Node The following example shows how to initialize VxVM the cluster node from which the command is issued. # clvxvm initialize Example 2 Initializing VxVM on a Cluster Node and Encapsulating the Root Disk The following example shows how to initialize VxVM and encapsulate the root disk on the cluster node from which the command is issued. # clvxvm encapsulate ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ FILES
/var/cluster/cmvxvm/* Location of temporary files that are used by the clvxvm utility. /var/cluster/logs/install/clvxvm.log.pid Log file that is created by the scvxinstall utility. SEE ALSO
Intro(1CL), cldevice(1CL), cldevicegroup(1CL), clsetup(1CL), cluster(1CL), scinstall(1M), scvxinstall(1M), rbac(5) Sun Cluster Software Installation Guide for Solaris OS NOTES
The superuser can run any forms of this command. Any user can also run this command with the following options: o -? (help) option o -V (version) option To run this command with other subcommands, users other than superuser require RBAC authorizations. See the following table. +------------+---------------------------------------------------------+ |Subcommand | RBAC Authorization | +------------+---------------------------------------------------------+ |encapsulate | solaris.cluster.modify | +------------+---------------------------------------------------------+ |initialize | solaris.cluster.modify | +------------+---------------------------------------------------------+ Sun Cluster 3.2 19 Jul 2006 clvxvm(1CL)
All times are GMT -4. The time now is 08:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy