TruCluster
cancel
Showing results for 
Search instead for 
Did you mean: 

vold does not start anymore !!!

Pier Paolo FRASSINO
Occasional Advisor

vold does not start anymore !!!

Hi,
I have a big trouble.
A 3 nodes cluster with v5.1B has one of its nodes crashed suddenly. Starting, this node is not able to restart vold any more and the error is:

May 20 16:56:21 maine vmunix: clsm: incoming CNX data: '
a^D'20 16:56:21 maine vmunix: clsm: checking for peer configurations
May 20 16:56:21 maine vmunix: Waiting for cluster mount to complete
May 20 16:56:21 maine vmunix: CNX QDISK: Successfully claimed quorum disk, adding 1 vote.
May 20 16:56:21 maine vmunix: clsm: checksum error detected after sync done
May 20 16:56:21 maine vmunix: clsm: sync retry due to checksum error
May 20 16:56:21 maine vmunix: clsm: checksum error detected after sync done
May 20 16:56:21 maine vmunix: clsm: sync failed due to persistent checksum error
May 20 16:56:21 maine vmunix: clsm: initialized
May 20 16:56:21 maine vmunix: vm_swap_init: swap is set to lazy (over commitment) mode
May 20 16:56:21 maine vmunix: vol_reset_kernel: remote failure.
May 20 16:56:21 maine vmunix: CMS: Joining deferred filesystem sets
May 20 16:56:21 maine vmunix: WARNING: cfs_devlist_update: could not enumerate advfs devts (err 2) for domain provawas_dmn
May 20 16:56:21 maine vmunix:
May 20 16:56:21 maine vmunix: WARNING: cfs_attached_to_devs: LSM not ready on this node yet so can't attempt to failover
May 20 16:56:21 maine vmunix:
May 20 16:56:21 maine vmunix: WARNING: cfs_attached_to_devs: LSM not ready on this node yet so can't attempt to failover
May 20 16:56:21 maine vmunix:
May 20 16:56:21 maine vmunix: WARNING: cfs_attached_to_devs: LSM not ready on this node yet so can't attempt to failover
May 20 16:56:21 maine vmunix:
May 20 16:56:21 maine vmunix: WARNING: cfs_attached_to_devs: LSM not ready on this node yet so can't attempt to failover
May 20 16:56:21 maine vmunix:
May 20 16:56:21 maine vmunix: vol_reset_kernel: remote failure.
May 20 16:56:21 maine vmunix: Releasing config lock on vold termination
May 20 16:56:21 maine vmunix: vol_reset_kernel: remote failure.
May 20 16:56:21 maine vmunix: Releasing config lock on vold termination


How can i try to fix this ???

Thanks in advance for any suggestion.

PierPa
4 REPLIES
John Manger
Valued Contributor

Re: vold does not start anymore !!!

What patch kit is the cluster running ?
Is this perhaps fixed in PK7 & PK8 ?

John M
Nobody can serve both God and Money
Pier Paolo FRASSINO
Occasional Advisor

Re: vold does not start anymore !!!

John,
I've not checked the patch release and I'm out of the office. But, even without the patch release, is possible to understand what a problem causes this error ? There is not a single word on it on the manuals, but we all know that entry in a logfile comes from a well known reason. Any suggestion about a direction to investigate ???

Thanks in advance

PierPa
Andrea Nenni
Occasional Advisor

Re: vold does not start anymore !!!

You're really trying to admin a TruCluster with LSM, one of the more complex architectures in the whole OS world, with manuals and posting a few log lines in a forum?
Pier Paolo FRASSINO
Occasional Advisor

Re: vold does not start anymore !!!

Hi everybody,
investigating with the customer it seems that this problem was previously addressed by HP. There is a patch available ( probably last patch bundle ) that we'll apply as soon as we'll receive it. The patch addresses synchronization LSM issues on a 3 node cluster ...

Up to now, we have the third node shutted down and all is ok.

Thanks.

PierPa