<div dir="ltr"><div><div>Hi Gianluca,<br><br></div>This sounds like a bug to me.<br></div>Can you please attach engine and vdsm logs?<br><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br>Thanks,<br></div>Idan<br></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Wed, Oct 18, 2017 at 4:41 PM, Gianluca Cecchi <span dir="ltr"><<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello,<div>on an FC based environment I have a powered off VM</div><div><br></div><div>Select VM --> disks subtab --> select one disk of 20Gb</div><div>move</div><div><br></div><div>at the end of the move apparently all went ok, but right after the "finished moving.." event I also get this error event</div><div><br></div><div>VDSM host1 command HSMGetAllTasksStatusesVDS failed: Cannot remove Logical Volume: (['Cannot remove Logical Volume: (u\'c5d360f5-cd90-4b3e-bdef-<wbr>924649bfbc5f\', "[\'2255c544-165b-4126-86ee-<wbr>70e6d1edef9a\']")'],)<br></div><div><br></div><div>After that I also do the same for another disk of the same VM with size 80Gb and it completes ok, without the same event error.<br></div><div>So the problem doesn't occur always</div><div><br></div><div>It seem to me that the old disk (aka old lv) has remained as a left over.</div><div><div>And in fact the source storage domain doesn't show 20Gb of more free space...</div></div><div>From the SPM host<br></div><div><br></div><div># lvs | egrep "VG|2255c544-165b-4126-86ee-<wbr>70e6d1edef9a"</div><div> LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert</div><div> 2255c544-165b-4126-86ee-<wbr>70e6d1edef9a 072feb00-bc16-416d-9a23-<wbr>39bde9cd3a94 -wi------- 20.00g </div><div> 2255c544-165b-4126-86ee-<wbr>70e6d1edef9a c5d360f5-cd90-4b3e-bdef-<wbr>924649bfbc5f -wi-ao---- 20.00g </div><div># </div><div><br></div><div>So it seems I have both the old LV on the original VG (2255c544-165b-4126-86ee-<wbr>70e6d1edef9a) and the LV on the VG related to the target storage domain</div><div><br></div><div>Is there any bug opened for this? How can I clean situation?</div><div>Thanks,</div><div>Gianluca </div><div><br></div><div><br></div></div>
<br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br></div></div>