Skip to main content
NetApp Knowledge Base

VASA Provider: "Flexvol was too small" during managed snapshot operation

  1. Last updated
  2. Save as PDF
Views:
110
Visibility:
Public
Votes:
0
Category:
netapp-vasa-provider
Specialty:
virt
Last Updated:

Applies to

VASA Provider 9.7.x and earlier

Issue

When attempting to take a managed snapshot of a virtual machine residing on a vVol datastore the following happens:

  • Snapshot operation fails with an exception during the prepareToSnapshotVirtualVolume API call 
  • An error similar to the following is seen in the vvolvp.log:

2020-11-20T05:08:06,728Z (INFO ) [cxf-53991:prepareToSnapshotVirtualVolume-7] Application {http://ws.vvol.vasa.netapp.com/}VASA#{http://com.vmware.vim.vasa/2.0/}prepareToSnapshotVirtualVolume has thrown exception, unwinding now: vasa.vim.vmware.com._2_0.StorageFault: Caused by: Caused by: Unable to find a location for a vVol of size 2,048 in storage container Test30 - Checked 1 places.  Specific reasons were iscsi_vol10 | Final Score: 0 | 100 -> 300 : Snapshot Bonus | 300 -> 300 : Max Luns On Node Penalty | 300 -> 300 : Max Luns Penalty | 300 -> 299 : Max Data Vvols Luns Penalty | 299 -> 0 : FlexVol iscsi_vol10 was too small. Volume of iscsi_vol10 has 1801875456 bytes available. 0 is space that is reserved and 2147483648 was requested.

 

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.