all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Gilberto Nunes <gilberto.nunes32@gmail.com>
Subject: Re: [pve-devel] Qm move_disk bug (?)
Date: Wed, 30 Sep 2020 15:22:12 +0200	[thread overview]
Message-ID: <39ec0356-5003-4996-07e6-09c02127bd6d@proxmox.com> (raw)
In-Reply-To: <CAOKSTBvPZV3gCaxx2cdBs-owp-LKHc_GZSrN+aP0QZOtQHzaOQ@mail.gmail.com>

Hey,

How did you move the disk? GUI or CLI?

If via CLI, could you post the command?

Additionally, which versions are installed? (pveversion -v)

One more question inline.

On 9/30/20 3:16 PM, Gilberto Nunes wrote:
> Hi all
> 
> I tried to move a vm disk from LVM-thin to a Directory Storage but when I
> did this, the qm move_disk just filled up the entire disk.

The VM disk (100G) or the physical disk of of the storage?

> The disk inside LVM-thin has 100G in size but only about 5G is occupied by
> the OS.
> I have used the qcow2 format.
> However, if I do it from CLI with the command:
> 
> qemu-img convert -O qcow2 /dev/pve/vm-100-disk-0
> /DATA/images/100/vm-100-disk-0.qcow2
> 
> It works nicely and just copied what the OS occupied inside the VM, but
> created a virtual disk with 100GB.
> 
> It's some kind of bug with qm move_disk???
> 
> Thanks a lot
> 
> ---
> Gilberto Nunes Ferreira
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
> 
> 




  reply	other threads:[~2020-09-30 13:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 13:16 Gilberto Nunes
2020-09-30 13:22 ` Aaron Lauterer [this message]
2020-09-30 13:26   ` Gilberto Nunes
2020-09-30 13:59     ` Gilberto Nunes
2020-09-30 14:21       ` Gilberto Nunes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39ec0356-5003-4996-07e6-09c02127bd6d@proxmox.com \
    --to=a.lauterer@proxmox.com \
    --cc=gilberto.nunes32@gmail.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal