unable to mount the LV

[Suresh Babu G]

# vgchange -a n vg01
vgchange: Volume group "vg01" has been successfully changed.
# vgchange -c y vg01
Performed Configuration change.
Volume group "vg01" has been successfully changed.
# cmrunpkg -v -n testserv1 pkg_1
Running package pkg_1 on node testserv1
The package script for pkg_1 failed with no restart. pkg_1 should not be restarted
Unable to run package pkg_1 on node testserv1
Check the syslog and pkg log files for more detailed information
cmrunpkg: Unable to start some package or package instances

[Horia Chirculescu]

And what about

pkg_1.cntl.log

?

[Suresh Babu G]

###### Node "testserv1": Package start failed at Tue Feb 9 17:34:21 IST 2010 ######

########### Node "testserv1": Starting package at Tue Feb 9 17:38:36 IST 2010 ###########
Feb 9 17:38:36 - Node "testserv1": Activating volume group vg01 with exclusive option.
Activated volume group in Exclusive Mode.
Volume group "vg01" has been successfully changed.
Feb 9 17:38:36 - Node "testserv1": Checking filesystems:
/dev/vg01/lvol1
file system is clean - log replay is not required
Feb 9 17:38:36 - Node "testserv1": Mounting /dev/vg01/lvol1 at /pkg_1
Feb 9 17:38:36 - Node "testserv1": Adding IP address 10.98.10.92 to subnet 10.98.10.0
cmmodnet: Unable to verify IP address 10.98.10.92.
cmmodnet: 10.98.10.92 might already be configured as a heartbeat IP or stationary IP address. Or it does not belong to subnet 10.98.10.0
ERROR: Function add_ip_address
ERROR: Failed to add IP address to subnet
Feb 9 17:38:36 - Node "testserv1": Remove IP address 10.98.10.92 from subnet 10.98.10.0
cmmodnet: IP address 10.98.10.92 is not configured on the subnet.
cmmodnet: Or IP address 10.98.10.92 is not valid.
cmmodnet: Use the "netstat -in" command to check the configured IP addresses
for the subnet.
ERROR: Function remove_ip_address
ERROR: Failed to remove 10.98.10.92
Feb 9 17:38:36 - Node "testserv1": Unmounting filesystem on /dev/vg01/lvol1
Feb 9 17:38:36 - Node "testserv1": Deactivating volume group vg01
Deactivated volume group in Exclusive Mode.
Volume group "vg01" has been successfully changed.
###### Node "testserv1": Package start failed at Tue Feb 9 17:38:36 IST 2010 ######

[Horia Chirculescu]

>10.98.10.92 might already be configured as a heartbeat IP or stationary IP address.

This indicates a misconfiguration on the IP addresses allocated to the cluster.
Check:

/etc/cmcluster/cmcluster.ascii

Maybe the 10.98.10.92 address is already set as a stationary address of the server?

Horia

[Horia Chirculescu]

Use the following command to verify the configuration you entered into the ascii file:

# cmcheckconf -v -C /etc/cmcluster/cmcluster.ascii

Should be verbose (-v). If you have errors, you should solve those.


Horia.

[Horia Chirculescu]

Afther you did that, you should re-constitue the binary configuration file with

cmapplyconf -v -C /etc/cmcluster/cmcluster.ascii


Horia.

[Suresh Babu G]

Hi Horia,

cmcheckconf is giving the below warning

Cluster cluster1 is an existing cluster
First cluster lock volume group /dev/vg01 needs to be designated as a cluster aware volume group.
cmcheckconf: Unable to verify cluster file: /etc/cmcluster/cmclconfig.ascii.

Thanks
Suresh

[Michael Steele_2]

Hi

"...First cluster lock volume group /dev/vg01 needs to be designated as a cluster aware volume group..."

Start over with your cluster.ascii file and properly fill out the template data fields, in particular to the cluster lock vg.

Question: Is this disk a lun or a local disk? Can it be seen by both nodes?

Question: Did you activate it properly? 'vgchange -a c /dev/vg01'. See volume group data filed in the cluster.ascii file, near the bottom.

This line, 'vgchange -a c' will be applied to all vg's listed here during the cmruncl command.

NOTE: Make sure ALL these vg's are deactivated 'vgchange -a n /dev/vg01' before cmruncl.