On Thu, Mar 17, 2016 at 11:35 AM, [email protected] <[email protected]> wrote: > I used that, but lock active in a few seconds again. > And oVirt do not update any VM's status
Unlocking entities is ok when you know that the operation that took the lock is finished or failed. This is a workaround for buggy operations leaving disks in locked state, not a normal way to use the system. We first must understand what is the flow that caused the snapshot to be locked, and why it remain locked. Please describe in detail the operations in the engine side, and provide engine and vdsm logs showing this timeframe. Nir > > Pa. > > > On 17.3.2016 10:26, Eli Mesika wrote: > > > > ________________________________ > > From: [email protected] > To: "users" <[email protected]> > Sent: Thursday, March 17, 2016 9:27:11 AM > Subject: [ovirt-users] question mark on VM ( DB status 8 ) > > Hello, > during backup What do you mean by "backup"? Can you describe how do you backup the vm? > VM hanged with question mark in ovirt and status 8 in DB, > snapshot file ( for backup )is locked. > How to clean snapshot locking a wake up this VM from "unknow" state ??? > > > Try using the unlock_entity.sh utility (run with --help for usage) > > > > regs. > pavel > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
