Skip to main content

We initiated a move a mount path operation on our cmvlt environment,but it seems that is stuck somehow .There is no other jobs running in that moment for this media agent.Also we can see that   all the data seems to be already copied.

We see 

Estimated Total Data Size:1.65 TB

Size of Data Copied:1:65 TB

are the same 

It is like this for 1 day and some hours 

Hi @Skenji , thanks for the post!

Can you check the cvma.log file on the Media Agent, and look for “movemountpath”?

there might be a large number of entries, so look for a consistent message.  Might be something like this depending on your error (I redacted some identifying info):

7356  b90   10/05 08:42:12 ####### movemountpath::GetFileChecksum() - Cannot Read Data from file \\<location>\CV_MAGNETIC\V_1061745\CHUNK_64913902, error=0xECCC0016:{CQiFile::Read(178)/ErrNo.22.(Invalid argument)}
7356  3380  10/05 08:42:12 ####### movemountpath::GetFileChecksum() - Cannot Read Data from file \\d<location>\CV_MAGNETIC\V_882417\CHUNK_47089978\SFILE_CONTAINER_104, error=0xECCC0016:{CQiFile::Read(178)/ErrNo.22.(Invalid argument)}
7356  23b0  10/05 08:42:12 ####### movemountpath::GetFileChecksum() - Cannot Read Data from file \\<location>\CV_MAGNETIC\V_1047948\CHUNK_62499894\SFILE_CONTAINER_049, error=0xECCC0016:{CQiFile::Read(178)/ErrNo.22.(Invalid argument)}
7356  1b50  10/05 08:42:12 ####### movemountpath::GetFileChecksum() - Cannot Read Data from file \\<location>\CV_MAGNETIC\V_785486\CHUNK_40561456\SFILE_CONTAINER_145, error=0xECCC0016:{CQiFile::Read(178)/ErrNo.22.(Invalid argument)}
7356  2f38  10/05 08:42:12 8216596 movemountpath::MoveStore() - Failed to write to file i\\<location>\CV_MAGNETIC\V_784481\CHUNK_40501461\SFILE_CONTAINER_016] on host OMA*ma*8400], error=0xECCC0016:{CQiFile::Write(225)/ErrNo.22.(Invalid argument)}, retry attempt m1]


Hello there 

Im not very good with reading the logs but i think there was some issue with the media agent at that time and still there is something that blocks this process to be completed.Because it is getting urgent we opened a case with support,will see...


Totally understandable!

Can you share the case number here so I can track it?

Thanks!!


Hello Mike ,thank you for interest from your side!
Incident 220919-141
Anyway our problem is solved 

It was just a matter of stopping the job and resubmit it again!
Maybe we were lucky but something was really hanging and before we look for professional support we did stop and resubmit the job but was still hanging 


These things happen!  I’m glad you were able to get it all resolved 🤓

Hope you come here the next time you have an issue or question!


Reply