Skip to main content
NetApp Knowledge Base

CONTAP-448664: iSCSI/FCP QoS Throttling and SCSI abort race can lead to a node disruption

  1. Last updated
    Jun 20, 2025
  2. Save as PDF
Views:
83
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
perf
Last Updated:
6/20/2025, 11:01:01 AM

Issue

iSCSI/FCP access control using QoS can cause a system panic if a request is being processed by QoS at the same time the last request for the QoS control point is being aborted by the iSCSI/FCP host.
If impacted, a panic string similar to this may be seen:

  • process on cpu16 hung (repl_Handle_reg) for 5007 milliseconds! in SK process repl_Handle_reg on release 9.16.1P3 (C)

 

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.