Skip to main content
NetApp Knowledge Base

Unable to create a volume due to missing MDV_CRS volume

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

Applies to

ONTAP 9

Issue

  • Cannot do any modification on the system because of missing MDV_CRS volumes
  • Creating a volume fails with an error:
 
Failed to create the volume on node "node_name". Reason: The MetroCluster or Vserver DR Configuration Replication Service is recovering. Issue the "metrocluster check config-replication show -instance" command or the "snapmirror config-replication status show" command and follow its guidance. If there is no guidance, wait a few minutes and then try the command again.
 
  • On SnapMirror destination cluster, SnapMirror relationship does not exist, but the source is trying to update MDV_CRS which does not exist
  • snapmirror config-replication status show reports error:

::*> snapmirror config-replication status show
                Enabled: true
                Running: false
         Storage Status: warning
         Storage In Use: Unavailable
        Storage Remarks: Unable to allocate resources due to error Unable to determine a suitable aggregate to create the Cluster Persistent Storage volume
        Vserver Streams: warning

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.