Re: [PVE-User] storage migration failed: mirroring error: VM xyz not running
2014-02-19 11:17 GMT+01:00 Angel Docampo : > Both in gluster and local? > Yes...glusterfs is a directory on the same filesystem of local storage (/var/lib/vz/glusterfs) -- Giampaolo Bozzali a.k.a Panda^(funk) - http://pandafunk.blogspot.com ___ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Re: [PVE-User] storage migration failed: mirroring error: VM xyz not running
Both in gluster and local? Then is not the allocsize mount option... I had an issue very similar toy you but I had XFS, I changed to ext4 and I solved it. Then I saw another guy who set allocsize=64k on his XFS and it also worked for him... but with ext3... :| Angel Docampo Datalab Tecnologia, s.a. Castillejos, 352 - 08025 Barcelona Tel. 93.476.69.10 - 6711 De: Giampaolo Bozzali Enviado: mi?rcoles, 19 de febrero de 2014 10:55 Para: Angel Docampo Cc: pve-user@pve.proxmox.com Asunto: Re: [PVE-User] storage migration failed: mirroring error: VM xyz not running 2014-02-19 10:48 GMT+01:00 Angel Docampo mailto:adoca...@dltec.net>>: What FS has under GlusterFS? XFS perhaps? no, it's an ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=0,data=ordered) -- Giampaolo Bozzali a.k.a Panda^(funk) - http://pandafunk.blogspot.com ___ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Re: [PVE-User] storage migration failed: mirroring error: VM xyz not running
2014-02-19 10:48 GMT+01:00 Angel Docampo : > What FS has under GlusterFS? XFS perhaps? > no, it's an ext3 (rw,relatime,errors=continue,user_xattr,acl,barrier=0,data=ordered) -- Giampaolo Bozzali a.k.a Panda^(funk) - http://pandafunk.blogspot.com ___ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Re: [PVE-User] storage migration failed: mirroring error: VM xyz not running
What FS has under GlusterFS? XFS perhaps? Angel Docampo Datalab Tecnologia, s.a. Castillejos, 352 - 08025 Barcelona Tel. 93.476.69.10 - 6711 De: pve-user-boun...@pve.proxmox.com en nombre de Giampaolo Bozzali Enviado: mi?rcoles, 19 de febrero de 2014 10:32 Para: pve-user@pve.proxmox.com Asunto: [PVE-User] storage migration failed: mirroring error: VM xyz not running Hello list, I'm getting this error while online moving a VM disk from glusterFS to local storage: create full clone of drive ide0 (limbo:401/vm-401-disk-1.qcow2) Formatting '/var/lib/vz/images/401/vm-401-disk-1.qcow2', fmt=qcow2 size=34359738368 encryption=off cluster_size=65536 preallocation='metadata' lazy_refcounts=off transferred: 0 bytes remaining: 34359738368 bytes total: 34359738368 bytes progression: 0.00 % transferred: 125829120 bytes remaining: 34233909248 bytes total: 34359738368 bytes progression: 0.37 % transferred: 293601280 bytes remaining: 34066137088 bytes total: 34359738368 bytes progression: 0.85 % transferred: 461373440 bytes remaining: 33898364928 bytes total: 34359738368 bytes progression: 1.34 % transferred: 482344960 bytes remaining: 33877393408 bytes total: 34359738368 bytes progression: 1.40 % TASK ERROR: storage migration failed: mirroring error: VM 401 not running The VM goes offline while transferring, it seems like the relative qemu process crashes with disks larger than 32GB since with smaller disks the move process goes fine. As I read in some other posts, I tried to set the local storage as 'shared' but it's the same. Offline migration works without problems, but I need to move online VMs :/ Someone had that problem and got it solved? Thanks! -- Giampaolo Bozzali a.k.a Panda^(funk) - http://pandafunk.blogspot.com ___ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
[PVE-User] storage migration failed: mirroring error: VM xyz not running
Hello list, I'm getting this error while online moving a VM disk from glusterFS to local storage: create full clone of drive ide0 (limbo:401/vm-401-disk-1.qcow2) Formatting '/var/lib/vz/images/401/vm-401-disk-1.qcow2', fmt=qcow2 size=34359738368 encryption=off cluster_size=65536 preallocation='metadata' lazy_refcounts=off transferred: 0 bytes remaining: 34359738368 bytes total: 34359738368 bytes progression: 0.00 % transferred: 125829120 bytes remaining: 34233909248 bytes total: 34359738368 bytes progression: 0.37 % transferred: 293601280 bytes remaining: 34066137088 bytes total: 34359738368 bytes progression: 0.85 % transferred: 461373440 bytes remaining: 33898364928 bytes total: 34359738368 bytes progression: 1.34 % transferred: 482344960 bytes remaining: 33877393408 bytes total: 34359738368 bytes progression: 1.40 % TASK ERROR: storage migration failed: mirroring error: VM 401 not running The VM goes offline while transferring, it seems like the relative qemu process crashes with disks larger than 32GB since with smaller disks the move process goes fine. As I read in some other posts, I tried to set the local storage as 'shared' but it's the same. Offline migration works without problems, but I need to move online VMs :/ Someone had that problem and got it solved? Thanks! -- Giampaolo Bozzali a.k.a Panda^(funk) - http://pandafunk.blogspot.com ___ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
Re: [PVE-User] Storage migration failed
> device-mapper: remove ioctl on failed: Device or resource busy Logical > volume "vm-146-disk-1" successfully removed > device-mapper: remove ioctl on failed: Device or resource busy TASK > ERROR: storage migration failed: mirroring error: VM 146 qmp command > 'block-job-complete' failed - The active block job for device 'drive-ide0' > cannot be completed I assume you do this when the VM is running? I also see similar problems, but never when I do it offline. Can you confirm this? Martin ___ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
[PVE-User] Storage migration failed
Sometimes while migrating VM from one storage to another (typical scenario is LVM on top of iSCSI -> LVM on top of iSCSI) i got this error right after copying disk image: --- device-mapper: remove ioctl on failed: Device or resource busy Logical volume "vm-146-disk-1" successfully removed device-mapper: remove ioctl on failed: Device or resource busy TASK ERROR: storage migration failed: mirroring error: VM 146 qmp command 'block-job-complete' failed - The active block job for device 'drive-ide0' cannot be completed --- Restart usually helps, but it's pretty annoying when you wait ~hr for some big VM to migrate and then after copy it throws this error and undo(?) all changes. Well at least it's not wiping original disk... Any ideas how to fix / prevent this? ___ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
