Cannot import/move disk from local-lvm to shared iscsi-lvm

What the hell... it works on the original LVM now?
Code: 
# pvesm alloc rackstation-iscsi-lvm 999 vm-999-disk-35 5G
  Logical volume "vm-999-disk-35" created.
successfully created 'rackstation-iscsi-lvm:vm-999-disk-35'

If I run the qm set command from my first post, it also runs further than before:
Code: 
# qm set 9000 --scsi0 rackstation-iscsi-lvm:0,import-from=/mnt/pve/rackstation/template/iso/noble-server-cloudimg-amd64.img
update VM 9000: -scsi0 rackstation-iscsi-lvm:0,import-from=/mnt/pve/rackstation/template/iso/noble-server-cloudimg-amd64.img
  Logical volume "vm-9000-disk-1" created.
transferred 0.0 B of 3.5 GiB (0.00%)
transferred 35.8 MiB of 3.5 GiB (1.00%)
transferred 71.7 MiB of 3.5 GiB (2.00%)
transferred 109.3 MiB of 3.5 GiB (3.05%)
transferred 145.2 MiB of 3.5 GiB (4.05%)
...
transferred 3.5 GiB of 3.5 GiB (99.25%)
transferred 3.5 GiB of 3.5 GiB (100.00%)
transferred 3.5 GiB of 3.5 GiB (100.00%)
can't create base images in lvm storage
# echo $?
255

I seemingly cannot create base images in LVM, is that true? local-lvm worked, though
 
LVM thin supports linked clones, LVM does not.
 
but what I actually wanted to let you try is (without LVM) discarding the LUN itself using various means, to see if that works or not ;)
 
SurfingEgg said:
I seemingly cannot create base images in LVM, is that true?
Click to expand...
No, your command should have worked fine as long as backend storage is cooperating.

Code: 
root@pve-1:~#  qm set 3033 --scsi0 sdb_group:0,import-from=/mnt/pve/bbnas/template/qcow/ubuntu-24.04-noble-server-cloudimg-amd64.img
update VM 3033: -scsi0 sdb_group:0,import-from=/mnt/pve/bbnas/template/qcow/ubuntu-24.04-noble-server-cloudimg-amd64.img
  Logical volume "vm-3033-disk-0" created.
transferred 0.0 B of 8.0 GiB (0.00%)
transferred 81.9 MiB of 8.0 GiB (1.00%)
...
transferred 8.0 GiB of 8.0 GiB (100.00%)
scsi0: successfully created disk 'sdb_group:vm-3033-disk-0,size=8G'

Code: 
root@pve-1:~# pvesm status
Name              Type     Status           Total            Used       Available        %
sdb_group          lvm     active        97652736         8388608        89264128    8.59%

root@pve-1:~# vgs
  VG        #PV #LV #SN Attr   VSize   VFree 
  sdb_group   1   1   0 wz--n- <93.13g <85.13g

root@pve-1:~# pvs
  PV             VG        Fmt  Attr PSize   PFree 
  /dev/sdb       sdb_group lvm2 a--  <93.13g <85.13g


ls -l /dev/disk/by-path/ | grep sdb
lrwxrwxrwx 1 root root  9 Jun 16 14:28 ip-172.16.200.41:3260-iscsi-iqn.2009-12.com.blockbridge:t-pexfzsbgfhkb-dmmkiahl-lun-0 -> ../../sdb


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
bbgeek17 said:
No, your command should have worked fine as long as backend storage is cooperating.
Click to expand...
the error would indicate that the VM in question is a template.. newly added disks are attempted to be converted to base images in that case, which is not available on all storage types.
 
  • Like
Reactions: bbgeek17
You must log in or register to reply here.
Top Bottom
Back