<div dir="ltr"><div><div><div><div>Hi Gianluca,<br><br></div>Can you try to reproduce it with FC? Maybe it's somehow related to that.<br></div>Did you try to lvremove the old lv's, or are they still in use?<br></div>Trying to do this from the SPM should be ok. What do you mean synchronize the information at the other node side?<br></div>In any case, this is a disk that you don't need anymore, isn't it? You said that the copy part of the move operation went well.<br></div><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>Regards,<br></div>Idan<br></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Thu, Oct 19, 2017 at 10:47 AM, 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"><span class=""><div class="gmail_extra"><div class="gmail_quote">On Thu, Oct 19, 2017 at 7:36 AM, Idan Shaby <span dir="ltr"><<a href="mailto:ishaby@redhat.com" target="_blank">ishaby@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><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="m_-7397144805312959318gmail-m_1646060373496704171gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br>Thanks,<br></div>Idan</div></div></div></div></div></div></div></div></div>
</blockquote></div><br></div></span><div class="gmail_extra">Hi Idan,</div><div class="gmail_extra">I have not at hand the full files right now, but these were the snippets I cut from vdsm log and engine.log yesterday around the time of the first error after sending the first e-mail</div><div class="gmail_extra">It seems vdsm reports that the logical volume is still in use while trying to remove it.... </div><div class="gmail_extra">I have tried to replicate on another environment also based on block storage, but now iSCSI and not FC and I was not able to get the error: the move disk operation of the powered off vm always completed successfully.</div><div class="gmail_extra">Both tests were done trying to move preallocated disks if that matters</div><div class="gmail_extra"><br></div><div class="gmail_extra">vdsm.log of host1</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_extra">2017-10-18 14:59:28,907+0200 ERROR (libvirt/events) [storage.TaskManager.Task] (Task='6331ec00-b75b-465e-<wbr>8d9c-04d465c09ea1') Unexpected error (task:872)</div><div class="gmail_extra">Traceback (most recent call last):</div><div class="gmail_extra"> File "/usr/share/vdsm/storage/task.<wbr>py", line 879, in _run</div><div class="gmail_extra"> return fn(*args, **kargs)</div><div class="gmail_extra"> File "<string>", line 2, in teardownImage</div><div class="gmail_extra"> File "/usr/lib/python2.7/site-<wbr>packages/vdsm/common/api.py", line 48, in method</div><div class="gmail_extra"> ret = func(*args, **kwargs)</div><div class="gmail_extra"> File "/usr/share/vdsm/storage/hsm.<wbr>py", line 3189, in teardownImage</div><div class="gmail_extra"> dom.deactivateImage(imgUUID)</div><div class="gmail_extra"> File "/usr/share/vdsm/storage/<wbr>blockSD.py", line 1289, in deactivateImage</div><div class="gmail_extra"> lvm.deactivateLVs(self.sdUUID, volUUIDs)</div><div class="gmail_extra"> File "/usr/share/vdsm/storage/lvm.<wbr>py", line 1304, in deactivateLVs</div><div class="gmail_extra"> _setLVAvailability(vgName, toDeactivate, "n")</div><div class="gmail_extra"> File "/usr/share/vdsm/storage/lvm.<wbr>py", line 843, in _setLVAvailability</div><div class="gmail_extra"> raise error(str(e))</div><div class="gmail_extra">CannotDeactivateLogicalVolume: Cannot deactivate Logical Volume: ('General Storage Exception: ("5 [] [\' Logical volume c5d360f5-cd90-4b3e-bdef-<wbr>924649bfbc5f/eff58f10-12bf-<wbr>412f-a5db-944bfb10904d is used by another device.\']\\nc5d360f5-cd90-<wbr>4b3e-bdef-924649bfbc5f/[\'<wbr>eff58f10-12bf-412f-a5db-<wbr>944bfb10904d\']",)',)</div><div>2017-10-18 14:59:28,907+0200 INFO (libvirt/events) [storage.TaskManager.Task] (Task='6331ec00-b75b-465e-<wbr>8d9c-04d465c09ea1') aborting: Task is aborted: 'Cannot deactivate Logical Volume: (\'General Storage Exception: ("5 [] [\\\' Logical volume c5d360f5-cd90-4b3e-bdef-<wbr>924649bfbc5f/eff58f10-12bf-<wbr>412f-a5db-944bfb10904d is used by another device.\\\']\\\\nc5d360f5-<wbr>cd90-4b3e-bdef-924649bfbc5f/[\<wbr>\\'eff58f10-12bf-412f-a5db-<wbr>944bfb10904d\\\']",)\',)' - code 552 (task:1177)<br></div><div><div>2017-10-18 14:59:28,908+0200 ERROR (libvirt/events) [storage.Dispatcher] FINISH teardownImage error=Cannot deactivate Logical Volume: ('General Storage Exception: ("5 [] [\' Logical volume c5d360f5-cd90-4b3e-bdef-<wbr>924649bfbc5f/eff58f10-12bf-<wbr>412f-a5db-944bfb10904d is used by another device.\']\\nc5d360f5-cd90-<wbr>4b3e-bdef-924649bfbc5f/[\'<wbr>eff58f10-12bf-412f-a5db-<wbr>944bfb10904d\']",)',) (dispatcher:81)</div></div><div><br></div><div>engine.log</div><div><div>2017-10-18 15:01:53,097+02 INFO [org.ovirt.engine.core.dal.<wbr>dbbroker.auditloghandling.<wbr>AuditLogDirector] (D</div><div>efaultQuartzScheduler6) [] EVENT_ID: USER_MOVED_DISK_FINISHED_<wbr>SUCCESS(2,010), Correlation ID: a8948cbf-80a</div><div>2-462d-8805-91da94868c6e, Job ID: ffba7504-a324-43ca-ab4c-<wbr>481610c1098b, Call Stack: null, Custom ID: null,</div><div> Custom Event ID: -1, Message: User gcecchi@internal-authz finished moving disk padora1_u01 to domain SATA</div><div>_ALLBCK.</div><div>2017-10-18 15:01:54,029+02 ERROR [org.ovirt.engine.core.dal.<wbr>dbbroker.auditloghandling.<wbr>AuditLogDirector] (DefaultQuartzScheduler5) [394f8568] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,<wbr>802), Correlation ID: null, Call Stack: null, Custom ID: null, Custom Event ID: -1, Message: 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\']")'],)</div><div>2017-10-18 15:01:54,029+02 INFO [org.ovirt.engine.core.bll.<wbr>tasks.SPMAsyncTask] (DefaultQuartzScheduler5) [394f8568] SPMAsyncTask::PollTask: Polling task '8446a883-9bb0-40a5-b1eb-<wbr>8a919defe4c0' (Parent Command 'RemoveImage', Parameters Type 'org.ovirt.engine.core.common.<wbr>asynctasks.<wbr>AsyncTaskParameters') returned status 'finished', result 'cleanSuccess'.</div></div><div><div>2017-10-18 15:01:54,029+02 ERROR [org.ovirt.engine.core.bll.<wbr>tasks.SPMAsyncTask] (DefaultQuartzScheduler5) [394f8568] BaseAsyncTask::<wbr>logEndTaskFailure: Task '8446a883-9bb0-40a5-b1eb-<wbr>8a919defe4c0' (Parent Command 'RemoveImage', Parameters Type 'org.ovirt.engine.core.common.<wbr>asynctasks.<wbr>AsyncTaskParameters') ended with failure:</div><div>-- Result: 'cleanSuccess'</div><div>-- Message: 'VDSGenericException: VDSErrorException: Failed in vdscommand to HSMGetAllTasksStatusesVDS, error = Cannot remove Logical Volume: (['Cannot remove Logical Volume: (u\'c5d360f5-cd90-4b3e-bdef-<wbr>924649bfbc5f\', "[\'2255c544-165b-4126-86ee-<wbr>70e6d1edef9a\']")'],)',</div><div>-- Exception: 'VDSGenericException: VDSErrorException: Failed in vdscommand to HSMGetAllTasksStatusesVDS, error = Cannot remove Logical Volume: (['Cannot remove Logical Volume: (u\'c5d360f5-cd90-4b3e-bdef-<wbr>924649bfbc5f\', "[\'2255c544-165b-4126-86ee-<wbr>70e6d1edef9a\']")'],)'</div></div><div><br></div><div>Is there any command I can run to consistently remove the stale LVs? </div><div>As oVirt doesn't use clvmd I don't think it is sufficient to issue the remove lv from the SPM node.. How will "synchronize" the information at the other node side?</div><div><br></div><div>Thanks,</div><div>Gianluca</div><div><br></div></div></div>
</blockquote></div><br></div>