Skip to main content
NetApp Knowledge Base

CONTAP-83598: Setting a retention time of zero on a file in a SnapLock volume might cause storage system disruption

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

Issue

On a SnapLock volume, if the retention time on a file is set to zero, then as part of committing the file to WORM, the ctime of the file is temporarily set to minus one (-1).
If the volume has the autocommit scanner enabled,and if the file is accessed during this time either by the autocommit scanner or with client protocols, a race condition might cause a storage system disruption.

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.