Skip to main content
NetApp Knowledge Base

Discrepancies between VLDB and WAFL indicated in vreport, referencing duplicate volumes

  1. Last updated
    Feb 17, 2025
  2. Save as PDF
Views:
238
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:
2/17/2025, 10:40:43 PM

Applies to

  • ONTAP 9
  • Vreport

Issue

  • ActiveIQ may indicate discrepancies between VLDB and WAFL, recommending to run a debug vreport show command.
  • The command shows output indicating duplicate volumes:
::> set diag
::*> debug vreport show

aggregate Differences:

Name             Reason   Attributes
--------         -------  ---------------------------------------------------
aggr1            Present both in VLDB and WAFL with differences
                          Node Name: Cluster01-01
                          Aggregate UUID: c7ace4e9-8217-4438-959e-1e5cad07d203
                          Aggregate State: online
                          Aggregate Raid Status: raid_tec
                          Aggregate HA Policy: sfo
                          Is Aggregate Root: false
                          Is Composite Aggregate: true
                          Aggregate Bin Count: 1
                          Is Cloud-Mirrored Aggregate: false
                          Primary Object Store Name: object_store1
  Differing Attribute: Volume Count (Try to fix volume differences using vreport for volume, and check again.)
    WAFL Value: 157
    VLDB Value: 156

volume Differences:

Name             Reason   Attributes
--------         -------  ---------------------------------------------------
svm1:vol1        Present in VLDB and duplicate volumes in WAFL. Use vreport fix to update with the correct node for the volume
                          Node Name: Cluster01-01
                          Volume DSID:4554 MSID:2162007679
                          UUID: 955f89f6-3989-11ed-8efa-d039ea9229e2
                          Aggregate Name: aggr1
                          Aggregate UUID: c7ace4e9-8217-4438-959e-1e5cad07d203
                          Vserver UUID: 9b652765-012e-11ed-a0fe-d039ea2c6929
                          AccessType: DP_READ_ONLY
                          StorageType: REGULAR
                          Constituent Role: none

    Duplicate Volume Info:
    *VolName: svm1:vol1 DSID: 4637 Node Name: Cluster01-02 Aggregate Name: aggr2

  • Running debug vreport fix as recommended fails:

::*> debug vreport fix -type volume -object svm1:vol1
Error: command failed: Fixing svm1:vol1 not allowed: Reason: Head of family already exists for this MSID.


 

 

 

 

 

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.