Skip to main content
NetApp Knowledge Base

Long CPs from multiple aggregates when target disk for SDC is also sick

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

Applies to

  • ONTAP 9
  • Sick Disk Copy(SDC)

Issue

  • Long CPs are observed from multiple aggregates.

Wed Mar 23 11:09:11 CST [NAS01: wafl_exempt06: wafl.cp.toolong:error]: Aggregate NAS01_aggr0 experienced a long CP.
Wed Mar 23 11:09:11 CST [NAS01: wafl_exempt00: wafl.cp.toolong:error]: Aggregate Aggr14 experienced a long CP.

  • Disk(0a.01.4) returns back to the spare pool after completing testing successfully in Maintenance Center.
  • When a disk fails gracefully(sick disk copy),  disk (0a.1.4) becomes the target disk again.
data 4a.03.13 4a 3 13 SA:B 0 SAS 10000 857000/1755136000 858483/1758174768 (prefail, copy in progress)
-> copy 0a.01.4 0a 1 4 SA:A 0 SAS 10000 857000/1755136000 858483/1758174768 (copy 92% completed)
 
Wed Mar 23 06:20:50 CST [DC-P-118-B-18-NAS01: config_thread: raid.rg.diskcopy.start:notice]: /Aggr14/plex0/rg2: starting disk copy from 4a.03.13 to 0a.01.4. Reason: Disk replace was started..

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.