[pve-devel] Live storage migration v5

[Alexandre DERUMIER]

>>Just to let you know, I'll be on vacation for a week starting tomorrow. 

me too ;)

>>The big one is that I got disk errors afterwards. So the copying failed 
>>somewhere/somehow, but I can't investigate this right away. 
>>I also ended up with a set of multiple qcow2 and raw disks in the end, 
>>not sure whether it was sometimes converted and sometimes wasn't? Might 
>>have happened during my manual edits to get ipv6 to work though (the 
>>changes I mentioned in the other mail). 

Yes, maybe related
I don't have reproduce this kind of problem on my side.
I'll try to reproduce




>>And the old disks don't get deleted yet (which is useful during testing 
>>but should probably not be the default. But it might even be useful to 
>>make this optional (similar to how we have a delete flag in move_disk). 

Ok,will do. (I was unsure about default behaviour, I'll add delete flag)




----- Mail original -----
De: "Wolfgang Bumiller" <w.bumiller at proxmox.com>
À: "aderumier" <aderumier at odiso.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Mardi 25 Octobre 2016 13:30:57
Objet: Re: [pve-devel] Live storage migration v5

Just to let you know, I'll be on vacation for a week starting tomorrow. 
I've tested this a bit and ran into a few issues: 

The big one is that I got disk errors afterwards. So the copying failed 
somewhere/somehow, but I can't investigate this right away. 
I also ended up with a set of multiple qcow2 and raw disks in the end, 
not sure whether it was sometimes converted and sometimes wasn't? Might 
have happened during my manual edits to get ipv6 to work though (the 
changes I mentioned in the other mail). 

And the old disks don't get deleted yet (which is useful during testing 
but should probably not be the default. But it might even be useful to 
make this optional (similar to how we have a delete flag in move_disk). 

On Tue, Oct 25, 2016 at 09:52:58AM +0200, Alexandre Derumier wrote: 
> changelog: 
> 
> block-job-complete && block-job-cancel are async. 
> We need to check if block job is finished with query block job 
> 
> 
> _______________________________________________ 
> pve-devel mailing list 
> pve-devel at pve.proxmox.com 
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel