nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Volume Move same one cluster

DhonaAgungP

Hello Guys,

Maybe somebody any experience for same this case?

Please give me step for troubleshoot.

Find more posts tagged with

Accepted answers

paul_stejskal

How is performance on the source/destination node? That first one will need to finish first. The other possibility could be BRE throttling, which is expected if latency is higher.

Lastly, how much i/o is going on with that volume? It might be so busy it can't finish a cutover.

All comments

paul_stejskal

How is performance on the source/destination node? That first one will need to finish first. The other possibility could be BRE throttling, which is expected if latency is higher.

Lastly, how much i/o is going on with that volume? It might be so busy it can't finish a cutover.

JonathanGaudette

Run
::> vol move show -instance
to see the actual "warning" state

DhonaAgungP

Hello Paul,
after we check performance source destination node

DhonaAgungP

hello Jonathan,

Fyi

DhonaAgungP

where can i check snapshot capacity in node aggr_SASInternal

paul_stejskal

There may be room on disks but it could be reserved. Why are you moving to an already full aggregate? ONTAP won't perform well with being full.