Skip to main content
NetApp Knowledge Base

Volume move stuck waiting for destination to commit for days

  1. Last updated
  2. Save as PDF
Views:
466
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • Volume move

Issue

  • Volume move indicates "Volume move job committing destination"

    • Cutover Started:(1 of 3 attempts) (1.67GB Sent)::Volume move job committing destination.

    • Duration of move: 10 days 21:03

  • Volume move not progressing after monitoring increments for days.
  • Volume move cannot be paused, cancelled, or aborted due to volume is busy

::*> volume move abort -vserver Vserver-01 -volume vol1

Error: command failed: Volume is busy

  • Volume trigger-cutover failed:

::*> volume move trigger-cutover -volume vol1 -vserver Vserver-01

Error: command failed: The volume move operation for volume vol1 in vserver Vserver-01, is in cutover state. Try again when the job is in a cutover deferred or replication state.

  • No progress observed when de-throttling the move process.
  • No progress from performing an ARL to the partner node.
  • Unable to cancel the associated job

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.