Skip to main content
NetApp Knowledge Base

CONTAP-658195: FlexGroup constituents enter nvfailed state after double node failure with nvfail option off

  1. Last updated
  2. Save as PDF
Views:
9
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Issue

  • FlexGroup constituent volumes enter in-nvfailed-state=true after double node failure, even though nvfail option is off.
  • EMS logs show: wafl.vol.setting.in.nvfailed.state:error: Volume <volume_name> is marked as in-nvfailed-state: Nvlog jettisoned.
  • Affected volumes display in-nvfailed-state=true in volume show -fields nvfail,in-nvfailed-state output.
  • Data access to affected FlexGroup constituents is blocked until manual intervention.
  • Occurs after unclean shutdown and nvlog jettison on node reboot.
  • Other FlexGroup constituents on unaffected nodes remain in-nvfailed-state=false.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.