VMware converter V2V 錯誤 (return code 2)

[sanbis1983]

最近要繼續將舊的 VM 轉移到新的上面
(從 vSphere 5.1 轉到 vSphere 6.5)
但是這兩天測試其中一台搬遷的時候
搬到 97% 就失敗了~Orz

OS 本身是 CentOS 6.6
匯出 log 查詢以後
先是一堆檔案顯示 socket ignored
下面開始出現一堆訊息

--> /bin/tar_1.28: ./home/xxxxxxxx/public_html/assets/uploads/410x410/1346749463758A.jpg: Cannot write: No space left on device
--> /bin/tar_1.28: ./home/xxxxxxxx/public_html/plugin/ck/ckfinder/userfiles/images/20161205124006.jpg: Cannot open: No such file or directory
--> /bin/tar_1.28: ./home/lifeway: Cannot mkdir: No space left on device

最後看到的訊息中 status 顯示為

Exiting with failure status due to previous errors /usr/lib/vmware-converter/bin/ssh -z -F /usr/lib/vmware-converter/ssh.conf root@192.168.0.0-p 22 " tar --one-file-system --sparse -C '/' -cf - ." | /bin/tar_1.28 --numeric-owner --delay-directory-restore -C '/mnt/p2v-src-root/' -y -xf - (return code 2)'

不知道有沒有人遇過相同的問題可以指點一下是哪裡有問題?

[POCEH]

Whats about "No space left on device" message? Extend your volume size.

[patanassov]

'tar' needs some extra space to untar the file on the target. As Rosen suggested - increasing the volume size would help.

On the other hand - why don't you use V2V (with the source powered off)? Thus the volumes may remain as they are and tar won't be running at all.

[sanbis1983]

That is a problem

Because the user wants not to power off

Although it is still necessary to deactivate the database

I don't know about "No space left on device"

this message is which one don't have enough space ?

is source machine or destination machine

This is the source machine amount of space currently seen in the host.

[POCEH · Accepted solution]

The message "no space left" means "there is no free space in file system on destination", in this case for root volume. check this.

[sanbis1983]

Thank your reply~

After inspection, the space usage has reached 89%

Try to increase the space 10G. The converter is finally finished.