From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id C72A0627B9 for ; Wed, 30 Sep 2020 15:26:49 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B94F019A7A for ; Wed, 30 Sep 2020 15:26:49 +0200 (CEST) Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 8905D19A66 for ; Wed, 30 Sep 2020 15:26:48 +0200 (CEST) Received: by mail-qk1-x736.google.com with SMTP id c62so1344316qke.1 for ; Wed, 30 Sep 2020 06:26:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qDu3h8Tyq6gK9EZtgGQbV/n854USUN920pUO5eZq4UY=; b=Q6D0LmxYusiSYhNBe2zr6FtUvuh9AQmc1juLDeI1Q3+HMUfWfOpZvW0lOn5HYmZL7n s818zL23Uv9SmrCF4CGMGSxZZ5BlQCx91nH49z//UDlMMZk3y7uiEmW5my5t84I1R09+ lX+cexpsYBuplBUhfrjmPn2Bk/LDLbEDJAwd4TSyXV82ZRX5iBrZKplPhKoJPqtogBII slocjbqbJqky7Xlnyly5e3cLGMtd1qSCT+AnF4UdVRkR1ks4BGWAejcwzj5R58YofNQv c5gtzMRKU7pemMZQMRRc/WvhVLbX8TM+XXqM/yr2dujUKuBjo6ayltxIX4dCzlB/wcs5 yRYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qDu3h8Tyq6gK9EZtgGQbV/n854USUN920pUO5eZq4UY=; b=e9W150HxcsosazjeaA6AAU25qWZNRdaV4/ZSo+SgZ7NWlWOjGFDKh7FXiVq3BdJIaE OFhml7ttl5E/JySvEMZ6k1vBxP6ruLrpz8bbrcODEC523/iV5W9T9Tqi3fDTLzIOuKyz /zblp351mT7MWQAfEVYldppQHgPeZvez9LBEDluuuv7knE2gX/kztEVtYRJXY/CYut1x FJGbwAujAgRo4CW611QrPFku3Siqu6+pGk6XREflphxuQm1+OI8LaHTOb5OdI6p+Zh0r R3AF4U0v++jH9FypYoWAygoyTQ4Cv0Yn8xl4/8fy1qKOe28BmmPR1PbHDogCsBbn+r7I xyCQ== X-Gm-Message-State: AOAM532ckA63661RzwsuC9ofeLNYUkqY/wySmhNL5mzJrIIfXlv5iBRG NKiSioxSjG7Zxibca5cQ3QhE+lV3qZ51TqxyeoipMwDPTI3HkA== X-Google-Smtp-Source: ABdhPJzcDQ8YJbetbzgjXJz4jMNmlbt2eLP09YOLYsEcm7wzYeRzNxN6DgeqX/PB28iIq+M1jeuNwo7AOGrHAdAfNdc= X-Received: by 2002:ae9:ec14:: with SMTP id h20mr2449473qkg.180.1601472401472; Wed, 30 Sep 2020 06:26:41 -0700 (PDT) MIME-Version: 1.0 References: <39ec0356-5003-4996-07e6-09c02127bd6d@proxmox.com> In-Reply-To: <39ec0356-5003-4996-07e6-09c02127bd6d@proxmox.com> From: Gilberto Nunes Date: Wed, 30 Sep 2020 10:26:04 -0300 Message-ID: To: Aaron Lauterer Cc: Proxmox VE development discussion X-SPAM-LEVEL: Spam detection results: 0 AWL 0.050 Adjusted score from AWL reputation of From: address DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain FREEMAIL_ENVFROM_END_DIGIT 0.25 Envelope-from freemail username ends in digit FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider HTML_MESSAGE 0.001 HTML included in message RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [pve-devel] Qm move_disk bug (?) X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Sep 2020 13:26:49 -0000 >> How did you move the disk? GUI or CLI? Both. >From CLI qm move_disk 100 scsi0 VMS (VMS is the Directory Storage) Proxmox all up to date... pveversion -v proxmox-ve: 6.2-2 (running kernel: 5.4.65-1-pve) pve-manager: 6.2-12 (running version: 6.2-12/b287dd27) pve-kernel-5.4: 6.2-7 pve-kernel-helper: 6.2-7 pve-kernel-5.4.65-1-pve: 5.4.65-1 pve-kernel-5.4.34-1-pve: 5.4.34-2 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.4-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.16-pve1 libproxmox-acme-perl: 1.0.5 libpve-access-control: 6.1-2 libpve-apiclient-perl: 3.0-3 libpve-common-perl: 6.2-2 libpve-guest-common-perl: 3.1-3 libpve-http-server-perl: 3.0-6 libpve-storage-perl: 6.2-6 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.3-1 lxcfs: 4.0.3-pve3 novnc-pve: 1.1.0-1 proxmox-backup-client: 0.8.21-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.2-12 pve-cluster: 6.1-8 pve-container: 3.2-2 pve-docs: 6.2-6 pve-edk2-firmware: 2.20200531-1 pve-firewall: 4.1-3 pve-firmware: 3.1-3 pve-ha-manager: 3.1-1 pve-i18n: 2.2-1 pve-qemu-kvm: 5.1.0-2 pve-xtermjs: 4.7.0-2 qemu-server: 6.2-14 smartmontools: 7.1-pve2 spiceterm: 3.1-1 vncterm: 1.6-2 zfsutils-linux: 0.8.4-pve1 >>> The VM disk (100G) or the physical disk of of the storage? The VM disk has 100G in size, but the storage has 40G... It's just a lab... --- Gilberto Nunes Ferreira Em qua., 30 de set. de 2020 =C3=A0s 10:22, Aaron Lauterer escreveu: > 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 > > > > > >