Hi, Just for the record: setting STATE to 1, CLONING_OPS to 0 and set <CLONES/> in the body column for an images in CLONE or LOCKED state resets the state to READY for the image and it can be used once more.
It would be nice if there were some utility repair tools to do this kind of thing easily. Regards, Gerry On 04/02/2015 12:58, Gerry O'Brien wrote: > Hi, > > What needs to be set in the image_pool table body column to turn > state CLONE and LOCKED off? > > Regards, > Gerry > > > > On 03/02/2015 18:17, Gerry O'Brien wrote: >> Hi, >> >> Below is the XML of the source image database entry. If I change >> STATE to 1, CLONING_OPS to 0 and set <CLONES/>, will this fix the >> problem? If so, is there any utility that will allow me edit the XML and >> then update the database or will I have to update the database manually? >> >> Gerry >> >> >> >> <IMAGE> >> <ID>446</ID> >> <UID>0</UID> >> <GID>0</GID> >> <UNAME>oneadmin</UNAME> >> <GNAME>oneadmin</GNAME> >> <NAME>W7-VLab-BASE [No 3DSmax]</NAME> >> <PERMISSIONS> >> <OWNER_U>1</OWNER_U> >> <OWNER_M>1</OWNER_M> >> <OWNER_A>0</OWNER_A> >> <GROUP_U>0</GROUP_U> >> <GROUP_M>0</GROUP_M> >> <GROUP_A>0</GROUP_A> >> <OTHER_U>0</OTHER_U> >> <OTHER_M>0</OTHER_M> >> <OTHER_A>0</OTHER_A> >> </PERMISSIONS> >> <TYPE>0</TYPE> >> <DISK_TYPE>0</DISK_TYPE> >> <PERSISTENT>1</PERSISTENT> >> <REGTIME>1411742280</REGTIME> >> >> <SOURCE><![CDATA[/var/lib/one/datastores/1/1bec29452ead3d88c626f9c66aa849e1]]></SOURCE> >> >> <PATH><![CDATA[/var/lib/one/datastores/1/a1637afc98e4be57bb30fa87e6ee5694]]></PATH> >> <FSTYPE><![CDATA]></FSTYPE> >> <SIZE>1</SIZE> >> <STATE>6</STATE> >> <RUNNING_VMS>0</RUNNING_VMS> >> <CLONING_OPS>1</CLONING_OPS> >> <CLONING_ID>-1</CLONING_ID> >> <DATASTORE_ID>1</DATASTORE_ID> >> <DATASTORE>default</DATASTORE> >> <VMS/> >> <CLONES> >> <ID>756</ID> >> </CLONES> >> <TEMPLATE> >> <DEV_PREFIX><![CDATA[hd]]></DEV_PREFIX> >> <DRIVER><![CDATA[qcow2]]></DRIVER> >> <FSTYPE><![CDATA]></FSTYPE> >> </TEMPLATE> >> </IMAGE> >> >> >> >> >> On 03/02/2015 15:45, Gerry O'Brien wrote: >>> Hi, >>> >>> The oned (4.6.2) daemon was restarted during a clone and now the >>> source image is stuck in state CLONE and target image is stuck in state >>> LOCKED. The actual Linux copy completed so both images are OK. >>> >>> How to I reset them to the READY state? Is there an oneimage command >>> or does the database have to be modified. If the database has to be >>> modified are there maintenance commands to do this? >>> >>> I could recreate the image form the Linux file but there are >>> template references to the existing OpenNebula image. Also the image is >>> 100GB (Windows!). >>> >>> Any help would be appreciated. >>> >>> Regards, >>> Gerry >>> > -- Gerry O'Brien Systems Manager School of Computer Science and Statistics Trinity College Dublin Dublin 2 IRELAND 00 353 1 896 1341 _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org