Visit Our UNIX and Linux User Community

Operating Systems Solaris Cannot mount Veritas volumes after cluster patch. Post 302587707 by buggin on Thursday 5th of January 2012 04:47:17 PM
Old 01-05-2012
At this point I'll be happy just to get everything mounted again. I just attempted another restore and it looks like I may have made some progress except for the "argument expected" before it completed.When I do a vxdisk list all of the FLEXLINE devices are shown but if I try to mount one of the volumes it hangs for a long time without any errors. And I can't seem to import the disk group either. I am a little concerned about committing the changes unless there's some way I can verify this configuration for sure. Any ideas?


-bash-3.00# vxconfigrestore -p 1206045518.165.server02
Diskgroup 1206045518.165.server02 configuration restoration started ......

Installing volume manager disk header for FLEXLINE0_0 ...
Installing volume manager disk header for FLEXLINE0_1 ...
Installing volume manager disk header for FLEXLINE0_10 ...
Installing volume manager disk header for FLEXLINE0_11 ...
Installing volume manager disk header for FLEXLINE0_12 ...
Installing volume manager disk header for FLEXLINE0_13 ...
Installing volume manager disk header for FLEXLINE0_14 ...
Installing volume manager disk header for FLEXLINE0_2 ...
Installing volume manager disk header for FLEXLINE0_3 ...
Installing volume manager disk header for FLEXLINE0_4 ...
Installing volume manager disk header for FLEXLINE0_5 ...
Installing volume manager disk header for FLEXLINE0_6 ...
Installing volume manager disk header for FLEXLINE0_7 ...
Installing volume manager disk header for FLEXLINE0_8 ...
Installing volume manager disk header for FLEXLINE0_9 ...
Installing volume manager disk header for FLEXLINE0_15 ...
Installing volume manager disk header for FLEXLINE0_16 ...
Installing volume manager disk header for FLEXLINE0_17 ...
Installing volume manager disk header for FLEXLINE0_18 ...
Installing volume manager disk header for FLEXLINE0_19 ...
Installing volume manager disk header for FLEXLINE0_20 ...
Installing volume manager disk header for FLEXLINE0_21 ...
Installing volume manager disk header for FLEXLINE0_22 ...
Installing volume manager disk header for FLEXLINE0_23 ...
Installing volume manager disk header for FLEXLINE0_24 ...
Installing volume manager disk header for FLEXLINE0_25 ...
Installing volume manager disk header for FLEXLINE0_26 ...
Installing volume manager disk header for FLEXLINE0_27 ...
Installing volume manager disk header for FLEXLINE0_28 ...
Installing volume manager disk header for FLEXLINE0_29 ...

/etc/vx/bin/vxconfigrestore: test: argument expected
 
Test Your Knowledge in Computers #878
Difficulty: Medium
Memory allocation is less critical in a real-time operating system (RTOS) than in other operating systems.
True or False?

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
cmruncl(1m)															       cmruncl(1m)

NAME
cmruncl - run a high availability cluster SYNOPSIS
cmruncl [-f] [-v] [-n node_name...] [-t | -w none] DESCRIPTION
cmruncl causes all nodes in a configured cluster or all nodes specified to start their cluster daemons and form a new cluster. To start a cluster, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the cluster configuration file. See access policy in cmquerycl(1m). This command should only be run when the cluster is not active on any of the configured nodes. This command verifies the network configu- ration before causing the nodes to start their cluster daemons. If a cluster is already running on a subset of the nodes, the cmrunnode command should be used to start the remaining nodes and force them to join the existing cluster. If node_name is not specified, the cluster daemons will be started on all the nodes in the cluster. All nodes in the cluster must be available for the cluster to start unless a subset of nodes is specified. Options cmruncl supports the following options: -f Force cluster startup without warning message and continuation prompt that are printed with the -n option. -v Verbose output will be displayed. -t Test only. Provide an assessment of the package placement without affecting the current state of the nodes or packages. The -w option is not required with the -t option as -t does not validate network connectivity, but assumes that all the nodes can meet any external dependencies such as EMS resources, package subnets, and storage. -n node_name... Start the cluster daemon on the specified subset of node(s). -w none By default network probing is performed to check that the network connectivity is the same as when the cluster was config- ured. Any anomalies are reported before the cluster daemons are started. The -w none option disables this probing. The option should only be used if this network configuration is known to be correct from a recent check. RETURN VALUE cmruncl returns the following value: 0 Successful completion. 1 Command failed. EXAMPLES
Run the cluster daemon: cmruncl Run the cluster daemons on node1 and node2: cmruncl -n node1 -n node2 AUTHOR
cmruncl was developed by HP. SEE ALSO
cmquerycl(1m), cmhaltcl(1m), cmhaltnode(1m), cmrunnode(1m), cmviewcl(1m), cmeval(1m). Requires Optional Serviceguard Software cmruncl(1m)

Featured Tech Videos

All times are GMT -4. The time now is 02:16 PM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy