[one-users] Stopping persistent image corruption

[Richard Palmer]

Dear Fabian,


> Hello Richard
> 
> On 13.10.2011 12:06, Richard Palmer wrote:
> > 	After stupidly launching a VM using a persistent disc image twice,
> > 	I'm very grateful to e2fsck for cleaning up the ensuing filesystem
> > 	corruption, but wondered if there is anything I could put in the
> > 	template file to tell opennebula not to allow this to happen?. Some
> > 	sort of unique instance flag ?.
> 
> Strange, this should be done with this settings in the image 
> template (with OpenNebula 2.2.1, do not know about 3.0):
> 
> PUBLIC          = NO
> PERSISTENT      = YES
> 
> Check the output of 'oneimage show <image_id>' when one VM is 
> running with this image, it should show this (which should lock 
> the image for any other VM):

Ah right, makes sense. At the moment I'm still just using the VM 
templates to manage disc images and haven't got my image repository configured;
had planned to do that when I move to 3.0 but perhaps I should get on with
it now...

cheers,

Richard


-- 
Richard Palmer			| Centre for E-Research
				|  King's College London
richard.d.palmer at kcl.ac.uk	| 
Tel: 0207 848 1973 		|