#volume move stuck at 98% fabricpool
1 messages · Page 1 of 1 (latest)
that can have many reasons. For example heavy client-side I/O or open CIFS sessions.
Usually you can force the cutover, but I would check the event log and vol move show -instance for clues on why the cutover was delayed
I can force it but forcing might end up in a outage right , I don't want that to happen
And it just says cutover_hard_deferred.
Yeah the transfer can't complete in the timeout window.
did this just start? it will keep trying to cutover. Maybe give it a day (maybe you already have?) and it might find a lull in activity where it can cut over in the requisite amount of time
yeah, if it doesn't finish I would just force the cutover at some point when activity is low. it's no worse than forcing a takeover (i.e. I/O freezes for a couple seconds)
If force cutover is there any estimate time which I can expect it to be completed??
Don't think so.