Skip to main content
NetApp Knowledge Base

ONTAP Select reboots with error maytag.ko::disk_io_done

  1. Last updated
  2. Save as PDF
Views:
49
Visibility:
Public
Votes:
0
Category:
ontap-select
Specialty:
ontapselect
Last Updated:

Applies to

  • ONTAP Select
  • High Availability (HA)

Issue

  • ONTAP Select node unplanned reboot
  • EMS logs show WAFL processes blocked due to backend storage unresponsive.
sched_monitor: sk.hog.runtime:notice]: Process wafl_exempt02 ran for 16059 milliseconds
sched_monitor: mgr.stack.longrun.proc:notice]: Long running process: wafl_exempt02
sched_monitor: sk.hog.runtime:notice]: Process mpcleaner_thread2 ran for 17067 milliseconds
sched_monitor: mgr.stack.longrun.proc:notice]: Long running process: mpcleaner_thread2pha_remove002: 
  • The affected node rebooted to recover after losing access to virtual disks (expected)

mlm.array.lun.removed:notice]: Array LUN (...) is no longer being presented to this node.pha_main000:kern.shutdown.initiator:debug]: SK reboot was initiated by"maytag.ko::disk_io_done+2045".

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.