Volume move shows the error: Preparing source volume for cutover : Deduplication is not ready for volmove cutover
Applies to
- ONTAP 9
- OnCommand System Manager
- Volume move operation
Issue
- When trying to move a volume, the following error may be seen:
The volume move operation of volume 'vol1' in Vserver 'vserver1' to destination aggregate 'aggr1' did not enter the cutover phase. The system provided the additional explanation: 'Preparing source volume for cutover: Deduplication is not ready for vol move cutover'. After a short delay, the volume move operation will reattempt cutover entry. The job ID for the volume move job is '1234'.
- The
volume move showcommand may indicate the following:
cluster::> volume move show
Vserver Volume State Move Phase Percent-Complete Time-To-Complete
--------- ---------- -------- --------------------- ---------------- ------------------------
vserver1 vol1 healthy cutover_soft_deferred 98% Sat May 23 20:02:53 2020
- Using
volume move show -detailsindicates the following:
Detailed Status: Waiting to Cutover. (Preparing source volume for cutover: Deduplication is not ready for volmove cutover Sent)::Reason: 3.11TB Volume move job monitoring transfer of data.
sislog file (SIS-LOG.GZin AutoSupports) may show an error like the following:
Sat May 23 22:00:00 CST 2020 [Vserver UUID: 80dfdc3e-d89e-11e7-9c8d-00a098b8d178] /vol/vol1 [sid: 0] Error (A volume move operation is in progress. Use the "volume move show" command to view the status of the move. Retry this command when the move is complete. )
- In some instances, management logs (
mgwd.log)may indicate the volume move was successful:
Sat May 23 22:16:16 CST [node: mgwd: mgmt.vopl.move.done:notice]: The volume move job with ID '1234' on volume 'vol1' on Vserver 'vserver1' to destination aggregate 'aggr1' succeeded.
- The volume move operation may become stuck or hung and automatic cutover may not complete