<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Dear ON Developers,</div>
<div><br>
</div>
<div>Our ON configuration is a bit different from what ON manual assumes.</div>
<div>The following is my guess of how onevm cancel VM where this VM is from a persistent image and running in a host via shared transfer manager.</div>
<div><br>
</div>
<div>I believe the following two variables are assumed in ON standard deployment.</div>
<div>SRC=$IMAGE_REPOSITORY_PATH/</div>
<div>DST=$VM_DIR/vmid/images</div>
<div><br>
</div>
<div>In this case, onevm cancel will do</div>
<div><br>
</div>
<div>1. tm_mv.sh : mv $DST/disk.0 /var/log/one/vmid/disk.0</div>
<div> Note here that $DST/disk.0 is actually a link to $IMAGE_REPOSITORY_PATH/original_file</div>
<div>2. tm_delete.sh : rm –f $DST</div>
<div>3. Image Driver will invoke var/remote/image/fs/mv to try to /var/log/one/vmid/disk.0 to the same image in IMAGE_REPOSITORY_PATH</div>
<div> which will not happen because Image Drive will realize that these two are identical when running readlink command.</div>
<div><br>
</div>
<div>My guess is that, if this is true, this step "3" appears to be a bug.</div>
<div>In other words, in step "3", the mv should not be prevented because they have the same pathname.</div>
<div><br>
</div>
<div>Could ON developers check this?</div>
<div>(I might be wrong.)</div>
<div><br>
</div>
<div><br>
</div>
<div>Thank you.</div>
<div>Hyunwoo</div>
<div>FermiCloud Project</div>
<div><br>
</div>
<div><br>
</div>
</body>
</html>