VPLEX: How to address a stuck disk expansion

Summary: This article explains how to correct the issue of a disk expansion that was stuck for over a week.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Instructions

Issue:         
Disk expansion stuck for weeks   

  • The affected expansion-status shows as 'in-progress' on Cluster-1.
  • The volume coming from a Unity array shows 1.7T across clusters.
  • There is no running rebuild 
  • No suspicious events in the firmware logs or audit logs 

        

VPlexcli:/> ll /**/unity_voll282-283_abc123
clusters/cluster-1/virtual-volumes/unity_voll282-283_abc123:
Name                        Value
--------------------------  ----------------------------------------
block-count                 455344128
block-size                  4K
cache-mode                  synchronous
capacity                    1.7T
consistency-group           super_metro
expandable                  true
expandable-capacity         0B
expansion-method            storage-volume
expansion-status            in-progress <<<<<
health-indications          []
health-state                ok
locality                    distributed
operational-status          ok
recoverpoint-protection-at  []
recoverpoint-usage          -
scsi-release-delay          0
service-status              running
storage-tier                -
supporting-device           device_voll282-283_vmax123_000d_123_1
system-id                   voll282-283_vmax123_000d_123
thin-capable                false
thin-enabled                unavailable
volume-type                 virtual-volume
vpd-id                      VPD83T3:60001440000000xxxxxxxxxe2957f9a6

/clusters/cluster-2/virtual-volumes/unity_vol282-283_abc123:
Name                        Value
--------------------------  ----------------------------------------
block-count                 455344128
block-size                  4K
cache-mode                  synchronous
capacity                    1.7T
consistency-group           super_metro
expandable                  true
expandable-capacity         0B
expansion-method            storage-volume
expansion-status            - <<<<<
health-indications          []
health-state                ok
locality                    distributed
operational-status          ok
recoverpoint-protection-at  []
recoverpoint-usage          -
scsi-release-delay          0
service-status              running
storage-tier                -
supporting-device           device_voll282-283_vmax123_000d_123_1
system-id                   unity_voll282-283_abc123
thin-capable                false
thin-enabled                unavailable
volume-type                 virtual-volume
vpd-id                      VPD83T3:60001440000000xxxxxxxxxe2957f9a6


The expansion status stating 'in-progress' is a cosmetic issue on the virtual-volume context. 


Hierarchy of the volume:
VPlexcli:/> show-use-hierarchy /clusters/cluster-1/virtual-volumes/unity_voll282-283_abc123
storage-view: super_metro_S12A (cluster-2)
storage-view: super_metro_S12A (cluster-1)
  consistency-group: super_metro(synchronous)
    virtual-volume: unity_voll282-283_abc123 (1.7T, distributed @ cluster-1, running)
      distributed-device: device_voll282-283_vmax123_000d_123_1 (1.7T, raid-1)
        distributed-device-component: device_voll282-283_vmax123_000d_163_12016Jan21_101557 (1.7T, raid-0, cluster-2)
          extent: extent_s12_unity_voll282-283_abc123_1 (1.7T)
            storage-volume: s12_unity_voll282-283_abc123 (1.7T)
              logical-unit: VPD83T3:60060160xxxxxxxxxxxxxxxa3f2f00e1
                storage-array: EMC-CLARiiON-CKM00xxxxxxxxx
        distributed-device-component: device_voll282-283_vmax1234_72e2_140_1 (1.7T, raid-0, cluster-1)
          extent: extent_r10_unity_voll282-283_abc123_1 (1.7T)
            storage-volume: r10_unity_voll282-283_abc123 (1.7T)
              logical-unit: VPD83T3:60060160xxxxxxxxxxxxxxxa635f6173
                storage-array: EMC-CLARiiON-CKM00xxxxxxxxx
            
            
Resolution:
Restarting the VPlex Management Console is required for VPlex to correctly reflect the 'expansion-status'. After restarting the VPlex Management Console, the expansion-status will be blank as it is expected unless there is an on-going expansion. 

Restarting the VPlexManagement Console: 
 
service@ManagementServer:~> sudo /etc/init.d/VPlexManagementConsole restart
Restarting EMC VPlex Management Console...                   done
                
                
Once the VPlex Management Console process has been stopped and started check the status to ensure it is running again.
 
service@ManagementServer:/etc/init.d/> sudo /etc/init.d/VPlexManagementConsole status
VPlexManagementConsole is running (pid 12345)
 
After restarting the VPLEX Management Console, wait for 1-2 minutes to allow the system to stabilize before attempting a new login.
 
After Restarting the VPLEX ManagementConsole :
                
VPlexcli:/> ll /**/unity_voll282-283_abc123
/clusters/cluster-1/virtual-volumes/unity_voll282-283_abc123:
Name                        Value
--------------------------  ----------------------------------------
block-count                 455344128
block-size                  4K
cache-mode                  synchronous
capacity                    1.7T
consistency-group           super_metro
expandable                  true
expandable-capacity         0B
expansion-method            storage-volume
expansion-status            - <<<<<<
health-indications          []
health-state                ok
locality                    distributed
operational-status          ok
recoverpoint-protection-at  []
recoverpoint-usage          -
scsi-release-delay          0
service-status              running
storage-tier                -
supporting-device           device_voll282-283_vmax123_000d_123_1
system-id                   unity_voll282-283_abc123
thin-capable                false
thin-enabled                unavailable
volume-type                 virtual-volume
vpd-id                      VPD83T3:60060160xxxxxxxxxxxxxae2957f9a6

/clusters/cluster-2/virtual-volumes/unity_voll282-283_abc123:
Name                        Value
--------------------------  ----------------------------------------
block-count                 455344128
block-size                  4K
cache-mode                  synchronous
capacity                    1.7T
consistency-group           super_metro
expandable                  true
expandable-capacity         0B
expansion-method            storage-volume
expansion-status            - <<<<<
health-indications          []
health-state                ok
locality                    distributed
operational-status          ok
recoverpoint-protection-at  []
recoverpoint-usage          -
scsi-release-delay          0
service-status              running
storage-tier                -
supporting-device           device_voll282-283_vmax123_000d_123_1
system-id                   unity_voll282-283_abc123
thin-capable                false
thin-enabled                unavailable
volume-type                 virtual-volume
vpd-id                      VPD83T3:60060160xxxxxxxxxxxxxae2957f9a6

Additional Information

If the issue still persists, please contact Dell EMC Customer Support and mention this article.

Affected Products

VPLEX Series

Products

VPLEX for All Flash, VPLEX GeoSynchrony, VPLEX VS2, VPLEX VS6
Article Properties
Article Number: 000019756
Article Type: How To
Last Modified: 06 Dec 2024
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.