lun.nvfail events

Contributors

LUN.nvfail.option.on

Severity

NOTICE

Description

This message occurs when the nvfail option for the named volume is turned on. The volume contains LUNs or NVMe namespaces and it is recommended that you keep this option on for such volumes.

Corrective Action

(None).

Syslog Message

The nvfail option for the volume %s (DSID %llu) has been turned on. The volume contains LUN or NVMe namespaces and it is recommended that this option be kept on for such volumes.

Parameters

volume_name (STRING): Name of the volume for which the nvfail option was turned on.
volume_dsid (LONGINT): Data Set ID (DSID) of the volume for which the nvfail option has been turned on.

LUN.nvfail.vol.proc.complete

Severity

ERROR

Description

This message occurs when an inconsistency is detected in the nvlog during boot or takeover, resulting in the initiation of nvfail processing and the LUNs in the volume being brought offline. This behavior is expected and is intended to prevent any FC/iSCSI data access to LUNs in a volume that might have lost the last few updates to the nvlog.

Corrective Action

Verify that the LUN maps are valid. After the LUNs are mapped properly, use the 'lun online' command to bring the LUNs online to make then available to hosts. Host side recovery actions may be required to check the consistency of the data in the LUNs.

Syslog Message

LUNs in volume %s (DSID %llu) have been brought offline because an inconsistency was detected in the nvlog during boot or takeover.

Parameters

volume_name (STRING): Name of the volume for which nvfail processing was completed.
volume_dsid (LONGINT): Data Set ID (DSID) of the volume for which nvfail processing was completed.

LUN.nvfail.vol.proc.failed

Severity

EMERGENCY

Description

This message occurs when nvfail processing for LUNs in a volume fails to complete. Some of the LUNs in the volume might not be offline. FC/iSCSI data access to the LUNs in the volume is prevented until the nvfail state of the volume is cleared.

Corrective Action

For any LUNs that are offline, use the 'lun online' command to bring them online and make them available to hosts. Host side recovery actions might be required to check the consistency of the data in the LUNs.

Syslog Message

An inconsistency was detected in the nvlog during boot or takeover, and some or all LUNs in volume %s (DSID %llu) might not have been brought offline.

Parameters

volume_name (STRING): Name of the volume for which LUN nvfail processing failed.
volume_dsid (LONGINT): Data Set ID (DSID) of the volume for which LUN nvfail processing failed.

LUN.nvfail.vol.proc.started

Severity

ERROR

Description

This message occurs when an inconsistency is detected in the nvlog during boot or takeover, resulting in the initiation of nvfail processing and the LUNs in the volume being brought offline. This behavior is expected and is intended to prevent any FC/iSCSI data access to LUNs in a volume that might have lost the last few updates to the nvlog.

Corrective Action

Verify that the LUN maps are valid. After the LUNs are mapped properly, use the 'lun online' command to bring the LUNs online to make then available to hosts. Host side recovery actions may be required to check the consistency of the data in the LUNs.

Syslog Message

LUNs in volume %s (DSID %llu) have been brought offline because an inconsistency was detected in the nvlog during boot or takeover.

Parameters

volume_name (STRING): Name of the volume for which nvfail processing was initiated.
volume_dsid (LONGINT): Data Set ID (DSID) of the volume for which nvfail processing was initiated.