The cluster partner
appears not to be
operational. You will
be asked whether you
want to continue. If
you answer "yes", the
existing cluster
monitor disk state
will be overwritten
and this node will be
rebooted. Answering
"no" will halt this
node with no
modification to the
cluster monitor disk
state.
WARNING: Answering
"yes" while the
cluster partner is
operational will have
unexpected and
potentially
catastrophic results:
YOUR FILESYSTEMS MAY
BE DESTROYED
Do you wish to
continue [y/n]?
|
The local filer has been taken over but it appears its partner is not operational. This message is usually preceded by the following message:
This node was
previously
declared dead.
Pausing to check
cluster
partner status ...
partner not
responding.
Thu Aug 13
16:58:37 GMT
[kbd_login_mgr]:
Login from console
|
Follow these steps:
- Verify that the partner is operational or
repair it.
- Reboot it.
- Perform a giveback from the partner.
Giveback is the only method to ensure that
data is consistent after a takeover.
- If you cannot repair the partner, perform one
of the following actions:
|
