Out of kernel memory

The user request failed because the kernel could not allocate sufficient memory to complete the request successfully. If possible, attempt the request again. If it continues to fail, this may indicate that the system has insufficient resources.

IBC error

On the Secondary, an attempt was made to dissociate or delete an rlink from an RVG against which there are outstanding IBC receive ioctls. All such outstanding ioctls must complete before the request will be processed.

Duplicate master_datavol mapping

Two volumes on the Secondary are mapped to the same volume on the Primary.

Multiple attached rlinks on Secondary

There could be some error during the recovery. The Secondary can only have one active rlink. Clear the utility fields and then dissociate any inactive rlinks.

Replicated volume may not have a drl

An attempt was made to associate a volume with the DRL log to an RVG. A volume with a DRL log is not allowed to be associated to an RVG.

SRL cannot be resized

This message is seen in the following unsupported scenarios:

V-5-1-3265 WARNING: DCM log size is smaller than recommended due to increased volume size.

This message is seen when a resize operation is executed on a volume which has a DCM plex attached with it. Due to the resize operation, because the volume size is bound to increase, the DCM plex size is increased to accommodate the increased volume length.

Action: To resize the DCM, remove the DCM plex from the existing configuration, then use the vxassist addlog command to create a DCM plex for the volume to set the correct size.

V-5-1-3265 WARNING: DCM log size will be smaller than recommended due to increased volume size.

The vxassist maxgrow command is used to find out the maximum size to which a volume can grow. If the volume has a DCM plex attached, vxassist calculates the DCM plex size that is required to accommodate the increased volume length .If this size is greater than the current size, this message displays.

Action: Remove DCM plexes from volume and add DCM plexes back specifying no loglen attribute, to get the default (recommended) size. Then re-issue the vxassist maxgrow command to find out how large the volume can be grown with the new DCM size.

VSet can not be associated to RVG for dg version less than 140

Indicates that the disk group for the RVG has a previous version that does not support associated volume sets.

To correct this error, upgrade the disk group using the following command:

# vxdg upgrade diskgroup

Rlink cannot be specified for making bunker secondary

Indicates that an rlink name was specified to the make Secondary command for a bunker RVG.

Action: Do not specify the rlink name in the makesecondary command for a bunker RVG.

Cannot make bunker rvg rvg_name a secondary because it has one attached rlink

A bunker Primary RVG cannot be converted to bunker Secondary RVG when it has an attached rlink. First detach the bunker Primary to the secondary rlink and then convert bunker Primary to bunker Secondary.

-b option is valid only for attaching rlink from bunker primary rvg.

"-b" option can only be used to connect rlink from bunker Primary to Secondary.

Only -a option is valid for attaching bunker rlinks from non-bunker primary

"-a" option can only be used to connect rlink from Primary to bunker Secondary.

Rlink rlink_name cannot be attached since bunker SRL doesn't contain updates to make secondary consistent after atomic commit.

Bunker site does not have enough data to perform replication to Secondary site, hence it can not be used to perform replication to Secondary site. This is possible only in certain limited situations where bunker site is not up to date as Primary due to network outage between Primary and bunker or bunker site down for some other reasons.

Rlink rlink_name cannot be attached since Bunker srl does not contain the update expected by secondary.

The next expected update on the Secondary is not available on the bunker SRL; therefore, you cannot use the bunker to perform replication to the Secondary site.

Rlink rlink_name cannot be attached because secondary has received more up-to-date writes already

Secondary site has received more up-to-date data than bunker site; therefore, you cannot use the bunker site to recover the Secondary.