[Linux-cluster] reboot to rejoin RAC cluster?

[Morrison, Bradley A]

Thanks for responding, Joel. It turned out to be a VLAN change which required a change with the bonded NIC. Immediately after issuing

   ifenslave -c bond-hb eth2

on the problem node, it joined the cluster and the OCFS volumes could be mounted.

-----Original Message-----
From: linux-cluster-bounces at redhat.com [mailto:linux-cluster-bounces at redhat.com] On Behalf Of Joel Becker
Sent: Thursday, January 06, 2011 4:03 PM
To: linux clustering
Subject: Re: [Linux-cluster] reboot to rejoin RAC cluster?

On Thu, Jan 06, 2011 at 12:01:32PM -0500, Morrison, Bradley A wrote:
> Q: Can I reboot one node in a two-node cluster and have it rejoin the cluster?

	You certainly should be able to.  You should not need a reboot
either if you just want to rejoin.

> I've a two-node cluster which recently had HBAs replaced on both cluster nodes.
> Node 1 was ejected sometime after its latest reboot, and now won't mount its OCFS volumes. The volumes' headers are verified from n1, i.e., it can see the volumes, but mounting fails. Restarting o2cb yields "modprobe: FATAL: Module ocfs2_stackglue not found."

	This sounds like a kernel configuration problem.  If you can't
load ocfs2_stackglue, you can't get the filesystem started.  What kernel
are you running?

Joel

-- 

"When arrows don't penetrate, see...
 Cupid grabs the pistol."

			http://www.jlbec.org/
			jlbec at evilplan.org

--
Linux-cluster mailing list
Linux-cluster at redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.

Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to European legal entities.