Storage configuration and space needed to import vhd

[dma]

Hi, I have a new server HPE ML350 G11 with 8 SSD, with hardware RAID 1+0 (6 disks + 2 online spare).
I've reserved 100 GB for the root partition and the remaining available space (5.76 TB) for LVM.

I have to import about 10 vms from a VirtualBox server, so I start copying a vdi vhd of 80 GB, then I executed 'qm importdisk' command to import and convert the vhd.
Now I've seen that my root partition is almost full, because it contains the copied 80 GB vdi vhd... ok, I can delete it after the import in lvm-thin, but the real problem is that I've other VirtualBox vms with vhd greater than 100 GB... how can I copy these files but not in the root partition?
Or... have I made a mistake in the partitioning of the space?
Thanks

 

[czechsys]

create LV in that LVM, format/mount.

 

[Impact]

There's some instructions about that here.

 

[dma]

create LV in that LVM, format/mount.

In the LVM there's already a LV of 5.6 TB named 'data'... I see it in Disks>LVM-Thin
But is it usable to copy the vhd from VirtualBox?

 

[Impact]

The idea is to create a LV inside the data thin pool as per link above.

 

[dma]

The idea is to create a LV inside the data thin pool as per link above.

Ok, I've understood... now it looks like this:

# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
data pve twi-aotz-- <5.09t 0.32 0.26
data2 pve Vwi-aotz-- 1000.00g data 1.67
root pve -wi-ao---- 96.00g
swap pve -wi-ao---- 8.00g

Is the newly created LV 'data2' visible in the Proxmox gui?

 

[Impact]

No. This is managed by you, not PVE.

 

[DzTimo]

Alternatively, you could set up an NFS share on the old server and mount it into your Proxmox server. Then you can run qm importdisk directly from the NFS share.

 

[dma]

No. This is managed by you, not PVE.

Ok.

I want to see the free space available:
# df -h
Filesystem Size Used Avail Use% Mounted on
udev 126G 0 126G 0% /dev
tmpfs 26G 2.5M 26G 1% /run
/dev/mapper/pve-root 94G 90G 8.8M 100% /
tmpfs 126G 46M 126G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
efivarfs 496K 245K 247K 50% /sys/firmware/efi/efivars
/dev/sda2 1022M 12M 1011M 2% /boot/efi
/dev/fuse 128M 16K 128M 1% /etc/pve
/dev/mapper/pve-data2 984G 28K 934G 1% /mnt/data2
tmpfs 26G 0 26G 0% /run/user/0

I see the LVs '/dev/mapper/pve-root' and '/dev/mapper/pve-data2', but why there is no mention of '/dev/mapper/pve-data'?

 

[Impact]

Please use code blocks

why there is no mention of '/dev/mapper/pve-data'?

Because the data volume is not mounted and does not contain a file system itself. Maybe looking at lsblk -o+FSTYPE helps you make sense of this.

 

[dma]

Please use code blocks

View attachment 88669


Because the data volume is not mounted. Maybe looking at lsblk -o+FSTYPE helps you make sense of this.

Sorry for code blocks... my mistake.

Thanks for all your support!

 

[gfngfn256]

Simplest way (I've done it, many times):

Copy necessary files to external USB drive, attach to server & mount in directory & then qm disk import <vmid> <source> <storage> [OPTIONS] from there (using the correct storage target).