Skip to main content
NetApp Knowledge Base

How do storage efficiencies affect volume move?

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

Applies to

  • ONTAP 9

Answer

  • When a volume is moved, the footprint it takes up does not include the storage efficiencies at the aggregate level.
    • The space will be inflated when moved to a new aggregate until the storage efficiencies can finish once the move is complete.
    • Example:
      • A volume could be 5 TB in actual disk space used, but really be 50 TB when excluding the space savings.
      • The destination aggregate only has 20 TB of free space.
      • This will fail as the volume really is using 50 TB of disk capacity, not 5 TB.
  • To view this footprint, use the volume show-footprint command and check the total Footprint in Performance Tier output.
    • Notes: 
      • If using volume show-footprint -fields, the flag is volume-blocks-footprint-bin0.
      • If using volume show-footprint with no -fields flag, it shows up as line item Footprint in Performance Tier.
  • This footprint will be compared to the aggregate's free space (such as using df -A -h).

Example:

    • Show the actual used space of the volume, not accounting for any FabricPool tiering:

     Cluster::> volume show-footprint -fields volume-blocks-footprint-bin0 

          Vserver : fsx
          Volume  : fg_oss_1712544968__0001

          Feature                                         Used       Used%
          --------------------------------             ----------    -----
          Volume Data Footprint                           512.1MB       0%

    • Compare with the aggregate free space, and see that 95.7 TB is clearly less than the 98.3 TB used above, so volume move will fail as it needs another 2.6 TB or more:

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

    Additional Information

    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.