Ad hoc solution: you can do 'xe-toolstack-restart' to
restart xapi.
But to be honesty, XCP/XenServer do have horrible control
over any IO operations. If something is going wrong, you can or reboot
everything, hoping this helps, or dig inside SM internals.
On
16.07.2012 05:56, Tianpeng Zhang wrote:
Hi all,
I met one issue that when using "xe export" command to export the image
to NFS disk, if we interrupt the process abnormally, shell will have no
response to any xe command.
The steps to reproduce this issue are like following:
1.
xe vm-export vm=$uuid_snapshot filename=$dir_xva/$name_xva.xva
($dir_xva is a NFS disk)
2. For some reason, $dir_xva does not have enough space to store this
image, so I use Ctrl+C to stop xe export process.
3. Then when typing any xe command, shell does not have any
response.
Has anybody met this problem before? Reboot the XCP host can fix the
problem, but this will interrupt all working state of existing VMs.
Thanks,
Tianpeng
_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api
