Skip to main content
NetApp Knowledge Base

Recurring “wafl.cp.toolong:error” Events and NFS Write Failures After ONTAP Upgrade

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

Applies to

  • NetApp AFF-A700
  • ONTAP 9.14.1P9, 9.15.1P11
  • Clusters with NFS workloads and scheduled backups.
  • Customers experiencing “wafl.cp.toolong:error” and NFS writev failed (error no.32) during backup snapshot deletes

Issue

  • After upgrading to ONTAP 9.14.1P9 (and persisting in 9.15.1P11), customers observed recurring “wafl.cp.toolong:error” messages in the event log, most frequently during backup windows. These events coincided with NFS clients reporting write failures (error no.32, “broken pipe”) in their kernel logs.

Typical log output:

FriAug1205:23:26+0200 [node1:wafl_exempt02:wafl.cp.toolong:error]: Aggregate aggr1_xxxxxxxxx experienced a long CP.
Oct1705:24:46 h3020022SAPSLI_74[15390]: Q0IBasisSystem: Operating system call writev failed (error no.32)

  • The errors occur when backup software deletes snapshots after nightly backups, causing WAFL to trigger long consistency points (CP).
  • NFS clients experience write failures during these long CPs, but no measurable latency or production impact was reported.

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.