跳转到主内容

对于集群节点上的任何卷,不会按照计划执行 Snapshot 副本

Views:
17
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

适用于

  • ONTAP 9 (所有版本)
  • ONTAP 9.1 ( 9.1p9 之前的所有版本)

问题

此问题可以通过三种方式表现出来:

1. 对于受影响节点上的所有卷、包括问题启动后创建的卷、自动创建卷 Snapshot 副本失败。没有快照策略或计划生成 Snapshot 副本。手动创建快照不会产生任何问题。

2. 不会删除卷快照。最后、我们达到 255 个快照的限制、不能再执行、手动或其他操作。

在本场景中、 手动创建快照失败并显示以下内容:

cluster1::> volume snapshot create -vserver vserver_name -volume volume_name -snapshot snap_name

Error: command failed: Failed to create snapshot "snap_name" of volume "volume_name" on Vserver "vserver_name". Reason: Cannot
       exceed maximum number of Snapshot copies.


通过运行以下命令可以在事件日志中看到自动创建快照失败:

cluster1::> event log show -node cluster1-01 -message-name wafl.snap.create*
Time                Node             Severity      Event
------------------- ---------------- ------------- ---------------------------
6/7/2018 21:05:00   cluster1-01      NOTICE        wafl.snap.create.skip.reason: vol18ee7c9be-036f-11e7-aa76-005056920d02: skipping creation of hourly.2018-06-07_2105 Snapshot copy (Cannot exceed maximum number of Snapshot copies.).


3. 系统出现紧急情况并显示类似以下内容的消息:

Sun Feb 04 22:00:07 GMT [cluster1-01: snapd_cmode: sk.panic:alert]: Panic String: process on cpu2 hung (snapd_cmode) for 5003 milliseconds! in SK process snapd_cmode on release 9.1 (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.