跳转到主内容

存储效率如何影响卷移动?

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

适用于

  • ONTAP 9

回答

  • 移动卷时,它占用的占用空间不包括聚合级别的存储效率。
    • 移动到新聚合时,空间将膨胀,直到移动完成后存储效率才能完成。
    • 示例:
      • 一个卷在实际使用的磁盘空间中可能是 5 TB,但通过空间节省实际上是 50 TB
      • 目标聚合只有 20 TB 的可用空间。
      • 此操作将失败,因为卷实际上正在使用 50 TB 的磁盘容量,而不是 5 TB。
  • 要查看此占用空间,请使用 volume show-footprint 命令并检查  Footprint in Performance Tier 输出。
  • 此占用空间将与聚合的可用空间(例如使用 df -A -h)进行比较。

示例:

    • 显示卷的实际已用空间,而不考虑任何 FabricPool 分层:

     Cluster::> volume show-footprint -fields volume-blocks-footprint-bin0
    vserver volume volume-blocks-footprint-bin0
    ------- ------ ----------------------------
    svm1   vol1  98.3TB

    • 与总可用空间相比,95.7 TB 明显小于上述使用的 98.3 TB,因此卷移动将失败,因为它需要 2.6 TB 或更多:

     Cluster::> aggr show -fields availsize
    aggregate availsize
    --------- ---------
    aggr1   95.7TB

    追加信息

    5/17/2021 12:57:29  Netapp-2     ERROR      mgmt.vopl.move.nospace: The 'volume move' operation with ID '14748' for volume 'volume_move' present on Vserver 'vserver' cannot proceed (Reason: Not enough space in the volume or aggregate).
    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.