ERROR

This message occurs when a high-availability (HA) controller failover (CFO) giveback is canceled due to RAID activity on a partner aggregate.

Reissue the "storage failover giveback" command to initiate giveback to the partner after the pending or in-progress operation on the partner volume or aggregate is complete. Use the "storage aggregate status -r" command to view the state of the aggregate. If a plex is offline, use the "storage aggregate plex online" command to bring the plex online. If unmirrored aggregates are not supported on this configuration, use the "storage aggregate mirror" command to mirror this aggregate.

%s %s%s is %s; canceling giveback.

vol_type (STRING): Volume type.
owner (STRING): Current owner of the aggregate.
vol (STRING): Name of the aggregate.
reason (STRING): Activity that is preventing CFO giveback.

NOTICE

This message occurs when AutoSupport vetoes a controller failover (CFO) giveback request because an AutoSupport message for the down partner node was not collected prior to the giveback request.

Typically, an AutoSupport message for the partner node is collected shortly after takeover is complete. If the CFO giveback was attempted and vetoed within 20 minutes of the takeover, retry the operation later. If time does not permit waiting, use the 'cf giveback -f' command to force a giveback.

AutoSupport vetoed giveback because an AutoSupport message for the down partner node was not yet collected.

(None).

NOTICE

This message occurs when the partner node is still dumping core, and cannot yet resume serving data. The giveback attempt has been canceled.

Either let the dumpcore operation finish, or use the "-override-vetoes true" parameter to force a giveback.

Giveback canceled because partner is still dumping core

(None).

NOTICE

This message occurs when savecore is currently saving the partner coredump. This work will be lost if a giveback is done at this time, so the giveback has been canceled.

Either let the savecore operation finish, or use the "-override-vetoes true" parameter to force a giveback.

Giveback canceled because savecore is running. %d%% - %d of %d blocks saved

percent (INT): Percentage of core that has been saved
completed (INT): Number of blocks that have been saved
total (INT): Total number of blocks in the core

NOTICE

This message occurs when savecore is getting ready to start saving the partner coredump. The giveback attempt has been canceled.

Either let the savecore operation finish, or use the "-override-vetoes true" parameter to force a giveback.

Giveback canceled because savecore is initializing

(None).

NOTICE

This message occurs when a giveback is forced that causes non-continuously available (non-CA) locks on the volume to be dropped. CA locks are established by opens through CIFS CA shares for regular files on read-write volumes that reside in controller failover (CFO) aggregates. These locks are mirrored to the node's high-availability (HA) partner to support the nondisruptive property of CA shares. The rest of the locks are classified as non-CA locks and are not mirrored to the node's HA partner.

(None).

Dropped non-CA locks on volume %s%s%s%s on CFO aggregate %s due to forced giveback.

owner (STRING): Volume owner.
vol (STRING): Volume name.
app (STRING): Application UUID.
volident (STRING): Unique identifier of the volume in cases where the volume name alone is insufficient.
aggrname (STRING): Aggregate name.

ERROR

This message occurs when a giveback has started but cannot proceed because non-continuously available (non-CA) locks are present on the volume. CA locks are established by opens through CIFS CA shares for regular files on read-write volumes that reside in controller failover (CFO) aggregates. These locks are mirrored to the node's high-availability (HA) partner to support the nondisruptive property of CA shares. The rest of the locks are classified as non-CA locks and are not mirrored to the node's HA partner.

Based on how resilient they are to failures, applications must either gracefully close sessions over which non-CA locks are established or accept lock state disruption. To determine the open files that have these sessions established, run the 'vserver cifs session file show -hosting-aggregate "aggregate list" -continuously-available No' command. "aggregate list" is a list of aggregates that are sent home as a result of the giveback operation. If lock state disruption for all existing non-CA locks is acceptable, retry the giveback operation by using the '-override-vetoes true' option.

Could not complete giveback because of non-CA locks on volume %s%s%s%s CFO aggregate %s.

owner (STRING): Volume owner.
vol (STRING): Volume name.
app (STRING): Application UUID.
volident (STRING): Unique identifier of the volume in cases where the volume name alone is insufficient.
aggrname (STRING): Aggregate name.

ERROR

This message occurs when the system cannot perform a giveback due to WAFL® NVSave file replay activity, and must abort the giveback.

Retry the giveback operation after completion of NVSave files replay. Replay completion is indicated by the EMS message 'wafl.nvsave.replaying.pass' or 'wafl.nvsave.replaying.fail'.

%s %s%s%s%s has WAFL NVSave file replay activity underway; canceling giveback.

type (STRING): Object type (volume or aggregate).
owner (STRING): Volume owner.
vol (STRING): Volume name.
app (STRING): Application UUID.
volident (STRING): To uniquely identify the volume in cases where the volume name itself is insufficient.

NOTICE

This message occurs when a cluster failover(CFO) giveback is vetoed by a critical replication transfer (for example, volume move in the cutover phase).

Either abort the replication transfer that is preventing the giveback from being completed, retry the 'storage failover giveback' command with the '-override-vetoes true' option, or wait for the transfer to finish.

Could not complete giveback because a replication transfer with UUID %s is in progress.

transferId (STRING): UUID of the SnapMirror® replication transfer that vetoed the giveback.

ERROR

This message occurs when a controller disallows a giveback attempt because the partner's disk ownership is being reassigned. Typically, ownership reassignment is done after a controller replacement.

Reissue the giveback request after disk ownership assignment is completed.

Giveback was vetoed because the disk ownership reassignment in progress on the partner cannot be interrupted.

(None).

NOTICE

This message occurs when the system cannot perform a giveback due to Snapshot(tm) copy activity, and must abort the giveback.

(None).

%s %s%s%s%s has Snapshot copy activity underway; canceling giveback.

type (STRING): Object type (volume or aggregate).
owner (STRING): Volume owner.
vol (STRING): Volume name.
app (STRING): Application UUID.
volident (STRING): To uniquely identify the volume in cases where the the volume name itself is insufficient.

NOTICE

This message occurs when the system detects Snapshot(tm) copy activity during giveback.

(None).

%s %s%s%s%s has Snapshot copy activity underway.

type (STRING): Object type (volume or aggregate).
owner (STRING): Volume owner.
vol (STRING): Volume name.
app (STRING): Application UUID.
volident (STRING): To uniquely identify the volume in cases where the the volume name itself is insufficient.

ERROR

This message occurs when a giveback is aborted because a failed disk is present.

Remove all failed disks and retry the giveback.

Failed disk %s should be removed before the giveback command is invoked.

diskName (STRING): Name of the device.

ERROR

This message occurs when a giveback is aborted because one or more bypassed disks are present.

Remove all bypassed disks and retry the giveback.

All bypassed disks should be removed before a giveback command is entered.

(None).

ERROR

This message occurs when a giveback is aborted because disk sanitization is in progress.

Retry the giveback after sanitization is completed.

Disk sanitization is in the process of formatting a disk. This operation should not be interrupted by a giveback.

(None).

ERROR

This message occurs when the vserver migrate cutover operation vetoes cfo aggregate giveback because vserver migration cannot be aborted during that time.

Reissue the 'storage failover giveback' command to initiate giveback to the partner when the vserver migrate cutover operation is completed.

Vserver migration in progress prevents giveback.

(None).