Skip to main content
NetApp Knowledge Base

SnapLock autocommit modify failing with value out of range error

  1. Last updated
  2. Save as PDF
Views:
41
Visibility:
Public
Votes:
0
Category:
snaplock
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9
  • SnapLock

Issue

  • Attempts to change the SnapLock autocommit period fails despite value being within the acceptable range
::> volume snaplock modify -autocommit-period 1114113 minutes -vserver svm1 -volume vol1
Error: command failed: The value specified with "-autocommit-period" must be in minutes (5 - 5256000) or hours (1 - 87600) or days (1 - 3650) or months (1 - 120) or years (1 - 10).
  • The autocommit-period of 1114113 minutes falls within the range of 5 - 5256000 minutes mentioned in the error, yet the command still fails
  • Due to a flaw in how autocommit-period values are calculated, this issue will occur for various values that fall within the specified range

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.