[PVE-User] NTFS/Windows Server corruption after successful livestorage migration

[Alexandre DERUMIER]

Hi, 

do you talk about "move disk" feature of proxmox ?

If yes, please test

http://download.proxmox.com/debian/dists/wheezy/pvetest/binary-amd64/qemu-server_3.3-3_amd64.deb

We have fixed a bug with storage migration

----- Mail original ----- 

De: "Chris Murray" <chrismurray84 at gmail.com> 
À: pve-user at pve.proxmox.com 
Envoyé: Jeudi 13 Novembre 2014 18:13:40 
Objet: Re: [PVE-User] NTFS/Windows Server corruption after successful livestorage migration 



Is it possible that a developer could comment on the mechanics of the online migration algorithm so that I know where to troubleshoot next? 

I did create a rudimentary test in Debian which would write alternate patterns of data while I migrated VMs back and forth. Between each pattern it will test the file to verify that it contains everything it should. This all seems to work fine and the problem isn’t reproducible. Could the problem be OS-specific? I’m not a developer but I would guess that the migration algorithm would be lower-level than this? 

Is it possible that the corruption could affect Windows machines while they’re under load and while they’re being migrated? It seems like it’s a factor of those three things. I don’t think it’s purely load as they do receive much higher load when e.g. at 03:00 all Windows virtual machines are subject to new updates. This doesn’t cause a problem; it only seems to be if I move a disk while it’s busy. Everything will tick along fine and the moment I have another corrupt VM I ask myself “what happened last?” and the answer is “I moved it” or “I changed file type”. 

Any ideas? 

Thanks, 
Chris 



From: pve-user [mailto:pve-user-bounces at pve.proxmox.com] On Behalf Of Chris Murray 
Sent: 05 November 2014 22:34 
To: Yannis Milios; pve-user at pve.proxmox.com 
Subject: Re: [PVE-User] NTFS/Windows Server corruption after successful livestorage migration 

Hi Yannis, 

I can try that, but what is it expected that either result will prove? 

If the VM is corrupt, what will that prove? What is the likely cause of the problem? 
If the VM is not corrupt, what will that prove? 

Thanks, 
Chris 


From: Yannis Milios [ mailto:yannis.milios at gmail.com ] 
Sent: 05 November 2014 20:44 
To: pve-user at pve.proxmox.com ; Chris Murray 
Subject: Re: [PVE-User] NTFS/Windows Server corruption after successful live storage migration 

hello, 
Never tried online storage migration but what happens if you do the following: 
1. create a windows vm in raw format, on local disk storage(not nfs mount). 
2. Start installing updates on windows and initiate online storage migration to the nfs mount in qcow2 format. 
Do you experience the same issue? 
referance: https://pve.proxmox.com/wiki/Storage_Migration 


No virus found in this message. 
Checked by AVG - www.avg.com 
Version: 2015.0.5315 / Virus Database: 4189/8510 - Release Date: 11/04/14 


No virus found in this message. 
Checked by AVG - www.avg.com 
Version: 2015.0.5315 / Virus Database: 4189/8510 - Release Date: 11/04/14 
_______________________________________________ 
pve-user mailing list 
pve-user at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user