Duplicate aggregates after HA pair relocation due to VLDB/WAFL inconsistency for SnapLock compliance disks

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 90

Visibility:: Public

Votes:: 0

Category:: aff-series

Specialty:: core

Last Updated:

Applies to

AFF/FAS
ONTAP 9

Issue

A cluster was reinitialize. Aggregates were found in a failed, partial state (Duplicate Aggregate)These aggregates were leftovers from a previous configuration and were offline due to missing RAID group disks.
When we tried to check aggregate status from cluster and node level, it was visible only on node level not on cluster level.

HSI_AFF_A250-02> aggr status Aggr State Status Options aggr0_HSI_AFF_A250_02 online raid_dp, aggr root, nosnap=on 64-bit HSIDEMO_02_NVME_SSD_1 failed raid_dp, aggr snaplock_compliance partial 64-bit Aggr1 failed raid_dp, aggr snaplock_compliance partial 64-bit HSI_AFF_A250-02> exit

HSI_AFF_A250::*> aggr show -fields snaplock-type
aggregate snaplock-type
--------- -------------
Aggr1     compliance
HSIDEMO_02_NVME_SSD_1 compliance
aggr0_HSI_AFF_A250_01 non-snaplock
aggr0_HSI_AFF_A250_02 non-snaplock
4 entries were displayed.
 
a) cluster shell view:
 HSI_AFF_A250::> aggr show

 aggr0_HSI_AFF_A250_01  159.9GB  7.75GB  95% online  1 HSI_AFF_A250-01 raid_dp
 aggr0_HSI_AFF_A250_02  159.9GB  7.75GB  95% online  1 HSI_AFF_A250-02 raid_dp

b) Node shell view :

 HSI_AFF_A250
 
 Aggregate HSIDEMO_02_NVME_SSD_1  (failed, raid_dp, partial)
     RAID group is missing 3 4 disks   OFFLINE/FAILED

 Aggregate Aggr1  (failed, raid_dp, partial)
     RAID group is missing 3 disks   OFFLINE/FAILED

 C) Spare disk inventory :

HSI_AFF_A250::> storage aggregate show-spare-disks

Original Owner: HSI_AFF_A250-02  Pool0
  1.0.3   847.3GB usable   1.75TB phys  (zeroed)
  1.0.23  847.3GB usable   1.75TB phys  (zeroed)

Could not delete duplicate/failing aggregates due to VLDB/WAFL discrepancies and SnapLock compliance constraints

Disk 0n.20 is a container disk, can't be spared. label makespare: Disk 0n.20P1 is part of a SnapLock Compliance volume. It will not be overwritten or formatted

Unpartitioning disks... Unpartition: Snaplock check failed for disk 0n.20 due to error (Disk 0n.20P1 is part of a SnapLock Compliance volume. It will not be overwritten or formatted).

Ran debug vreport show discrepancy, aggregate found in WAFL but not in VLDB.

 ::*> debug vreport show
aggregate Differences:

Name                                     Reason             Attributes
----                                     ------             ----------
Aggr1(b19d70bd-d994-11ef-bf0a-d039ea529877)
            Present in WAFL Only
              Node Name: HSI_AFF_A250-01
              Aggregate UUID: b19d70bd-d994-11ef-bf0a-d039ea529877
              Aggregate State: failed
              Aggregate Raid StatuElementss: raid_dp, partial
              Is Aggregate Root: false
              Is Composite Aggregate: false

  Duplicate Aggregate Info:
    Node Name: HSI_AFF_A250-02
    Aggregate UUID: b19d70bd-d994-11ef-bf0a-d039ea529877
    *Aggregate Name: Aggr1

HSIDEMO_02_NVME_SSD_1(a43dacee-4029-42ea-a104-d9438be01e9b)
            Present in WAFL Only
              Node Name: HSI_AFF_A250-01
              Aggregate UUID: a43dacee-4029-42ea-a104-d9438be01e9b
              Aggregate State: failed
              Aggregate Raid Status: raid_dp, partial
              Is Aggregate Root: false
              Is Composite Aggregate: false

  Duplicate Aggregate Info:
    Node Name: HSI_AFF_A250-02
    *Aggregate Name: HSIDEMO_02_NVME_SSD_1

2 entries were displayed.