Subscribe

Volume cannot delete after aggr has been deleted force...

Hi,

 

Env: cDOT832

 

when delete the data aggr force(an abnormal operaton...) without delete the volumes first. It left all the volumes and seems like cannot be deleted.

 

 

######volume show output:

 

 

nyn001f1  nyn001f1v1   -            -          RW            -          -     -

nyn001f1  nyn001f1v10_iscsi

                       -            -          RW            -          -     -

nyn001f1  nyn001f1v11_iscsi

                       -            -          RW            -          -     -

nyn001f1  nyn001f1v12_migrate_test2

                       -            -          RW            -          -     -

nyn001f1  nyn001f1v2   -            -          RW            -          -     -

nyn001f1  nyn001f1v3   -            -          RW            -          -     -

nyn001f1  nyn001f1v4   -            -          RW            -          -     -

nyn001f1  nyn001f1v5   -            -          RW            -          -     -

nyn001f1  nyn001f1v6   -            -          RW            -          -     -

nyn001f1  test_fcp     -            -          RW            -          -     -

nyn001f1  test_iscsi   -            -          RW            -          -     -

nyn001f1  vol1         -            -          RW            -          -     -

 

######try to delete the volumes....

 

nyn001c1::*> volume delete -volume nyn001f1v2 -vserver nyn001f1

 

Warning: Quota policy rules configured for this volume will be deleted. Are you sure you want to delete volume "nyn001f1v2" in Vserver "nyn001f1" ? {y|n}: y

[Job 3545] Initializing

Error: command failed: [Job 3545] Job failed: Unable to get information for volume "nyn001f1v2" on Vserver "nyn001f1". Reason: entry doesn't exist.

 

nyn001c1::*> volume delete -volume nyn001f1v2 -vserver nyn001f1 -force

[Job 3546] Initializing

Error: command failed: [Job 3546] Job failed: Unable to get information for volume "nyn001f1v2" on Vserver "nyn001f1". Reason: entry doesn't exist.

 

nyn001c1::*> volume delete -volume nyn001f1v2 -vserver nyn001f1 -force -disable-offline-check

[Job 3547] Initializing

Error: command failed: [Job 3547] Job failed: Unable to get information for volume "nyn001f1v2" on Vserver "nyn001f1". Reason: entry doesn't exist.

 

 

 

 

####vol detail information,

nyn001c1::*> vol show -volume nyn001f1v2 -instance

 

                                     Vserver Name: nyn001f1

                                      Volume Name: nyn001f1v2

                                   Aggregate Name: -

                                      Volume Size: -

                                     Name Ordinal: -

                               Volume Data Set ID: 1035

                        Volume Master Data Set ID: 2147484683

                                     Volume State: -

                                      Volume Type: RW

                                     Volume Style: flex

                           Is Cluster-Mode Volume: true

                            Is Constituent Volume: false

                                    Export Policy: default

                                          User ID: -

                                         Group ID: -

                                   Security Style: -

                                 UNIX Permissions: -

                                    Junction Path: -

                             Junction Path Source: -

                                  Junction Active: true

                           Junction Parent Volume: -

                              Vserver Root Volume: false

                               ........................

Re: Volume cannot delete after aggr has been deleted force...

Thats messy.  See if debug vreport show/fix helps things along.

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: Volume cannot delete after aggr has been deleted force...

I hope you found the solution to this already, but putting it out there for others who may have done this as well.

If you've force deleted the aggr and there is a orhpaned volume name, you have inconsistencies in VLDB and WAFL.

To view the inconsistencies

 

set -priv diag
debug vreport show

Result: list of consistencies

 

To fix the inconsistencies

set -priv diag
debug vreport fix -type volume -object svm_name:vol_name

Result: "This table is currently empty. Info: WAFL and VLDB volume/aggregate records are consistent."