> Jan Siml hat am 28. August 2015 um 19:52 geschrieben:
>
>
> Hello,
>
> >> > > > got exactly the same issue, with all nice side effects like
> > performance
> >> > > > degradation. Until now i was not able to fix this, or to fool the
> >> > engine
> >> > > > somehow that it whould show the image
Hello,
>> > > > got exactly the same issue, with all nice side effects like
> performance
>> > > > degradation. Until now i was not able to fix this, or to fool the
>> > engine
>> > > > somehow that it whould show the image as ok again and give me a 2nd
>> > > > chance to drop the snapshot.
>> > >
> Jan Siml hat am 28. August 2015 um 16:47 geschrieben:
>
>
> Hello,
>
> > > > got exactly the same issue, with all nice side effects like performance
> > > > degradation. Until now i was not able to fix this, or to fool the
> > engine
> > > > somehow that it whould show the image as ok again and
Hello,
> > got exactly the same issue, with all nice side effects like performance
> > degradation. Until now i was not able to fix this, or to fool the
engine
> > somehow that it whould show the image as ok again and give me a 2nd
> > chance to drop the snapshot.
> > in some cases this pro
> Jan Siml hat am 28. August 2015 um 15:15 geschrieben:
>
>
> Hello Juergen,
>
> > got exactly the same issue, with all nice side effects like performance
> > degradation. Until now i was not able to fix this, or to fool the engine
> > somehow that it whould show the image as ok again and give me
Hello Juergen,
got exactly the same issue, with all nice side effects like performance
degradation. Until now i was not able to fix this, or to fool the engine
somehow that it whould show the image as ok again and give me a 2nd
chance to drop the snapshot.
in some cases this procedure helped (ne
got exactly the same issue, with all nice side effects like performance
degradation. Until now i was not able to fix this, or to fool the engine somehow
that it whould show the image as ok again and give me a 2nd chance to drop the
snapshot.
in some cases this procedure helped (needs 2nd storage
Hello,
if no one has an idea how to correct the Disk/Snapshot paths in Engine
database, I see only one possible way to solve the issue:
Stop the VM and copy image/meta files target storage to source storage
(the one where Engine thinks the files are located). Start the VM.
Any concerns rega
Hello,
after a failed live storage migration (cause unknown) we have a
snapshot which is undeletable due to its status 'illegal' (as seen
in storage/snapshot tab). I have already found some bugs [1],[2],[3]
regarding this issue, but no way how to solve the issue within oVirt
> 3.5.3.
I have a
Further investigations showed, that the time on the target storage went
backwards due to a misconfigured NTP service. Someone has corrected the
configuration while live storage migration was running and the time
jumped backwards.
Might this be a cause for the issue?
Original Message
10 matches
Mail list logo
