On Thu, 20 Dec 2012 08:27:12 +0100
Michael Rasmussen wrote:
> Didn't new that. I will try later today.
>
I have done a number of test using various bs with dd. My test shows
that using qemu-img convert -t writeback makes qemu-img convert out
perm dd with roughly doing the job 15% faster:-)
qemu
On Thu, 20 Dec 2012 04:47:45 +
Dietmar Maurer wrote:
>
> Do you pass correct cache setting?
>
> # qemu-img convert -t writeback ...
>
Didn't new that. I will try later today.
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael rasmussen cc
http://pgp.mit.edu:11371/
> > maybe you can try with "qemu-img convert" (this is what I use In my
> > test code, you can also use qcow2 or any storage as input)
> >
> dd is 2-3 times faster than "qemu-img convert" given the right options.
Do you pass correct cache setting?
# qemu-img convert -t writeback ...
_
On Mon, 17 Dec 2012 18:31:05 +0100 (CET)
Alexandre DERUMIER wrote:
> maybe you can try with "qemu-img convert" (this is what I use In my test
> code, you can also use qcow2 or any storage as input)
>
dd is 2-3 times faster than "qemu-img convert" given the right options.
--
Hilsen/Regards
Mic
> 1) Copies the entire block device bit by bit even if bits are zero
> 2) Painfully slow due to 1)
But 1 is needed, because LVM does not initialize new volumes with zero.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-
om
Envoyé: Lundi 17 Décembre 2012 18:08:26
Objet: [pve-devel] Storage migration: LVM copy
Hi all,
Storage migrate to a LVM volume means, for all I know, using dd
if=current_image of=new_image bs=1M. For two reason I wish there were
some other way of doing it:
1) Copies the entire block de
Hi all,
Storage migrate to a LVM volume means, for all I know, using dd
if=current_image of=new_image bs=1M. For two reason I wish there were
some other way of doing it:
1) Copies the entire block device bit by bit even if bits are zero
2) Painfully slow due to 1)
Any other, faster, way of doing
