Just installed Proxmox VE 5.2-1, why /dev/mapper/pve-date isn't mounted?

JChris

New Member
Jul 2, 2018
2
0
1
28
I just installed Proxmox VE 5.2-1 and I have the following structure:
upload_2018-7-1_20-13-44.png

I copied some ISOs to local via GUI upload. By default, the ISOs I uploaded were sent to /var/lib/vz/template/iso:
upload_2018-7-1_20-16-17.png

I created two VMs and their disk images are stored on local-lvm, by default:
upload_2018-7-1_20-15-54.png

My df -h output is:

Code:
root@proxmox:~# df -h
Filesystem            Size  Used Avail Use% Mounted on
udev                  3.9G     0  3.9G   0% /dev
tmpfs                 796M  9.2M  787M   2% /run
/dev/mapper/pve-root   16G  6.4G  9.4G  41% /
tmpfs                 3.9G   63M  3.9G   2% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
tmpfs                 3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/sda2             253M  292K  252M   1% /boot/efi
/dev/fuse              30M   16K   30M   1% /etc/pve
tmpfs                 796M     0  796M   0% /run/user/0

My questions is, why isn't /dev/mapper/pve-data mounted? From what I understand the local-lvm should be my /dev/mapper/pve-data, because that's where my VM/Container data is stored. Am I wrong, is there something wrong in my setup? It's working, I just want to know if it's correct.
 
This new behavior is called thin-provisioning. You can see detail LVM using:
# lvdisplay

My lvdisplay result is:

Code:
root@proxmox:~# lvdisplay
  --- Logical volume ---
  LV Path                /dev/pve/swap
  LV Name                swap
  VG Name                pve
  LV UUID                lyIpd3-irLI-fQ8y-QOSe-v6sP-UcaA-h8BfUO
  LV Write Access        read/write
  LV Creation host, time proxmox, 2018-07-01 11:19:54 -0300
  LV Status              available
  # open                 2
  LV Size                7.00 GiB
  Current LE             1792
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:0

  --- Logical volume ---
  LV Path                /dev/pve/root
  LV Name                root
  VG Name                pve
  LV UUID                IjmXXq-SKDa-mITs-abVW-cBq8-vpTY-Xf941e
  LV Write Access        read/write
  LV Creation host, time proxmox, 2018-07-01 11:19:54 -0300
  LV Status              available
  # open                 1
  LV Size                15.75 GiB
  Current LE             4032
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:1

  --- Logical volume ---
  LV Name                data
  VG Name                pve
  LV UUID                J1k1cP-7xDS-Uisv-suim-CXMs-5FOM-lzoNp7
  LV Write Access        read/write
  LV Creation host, time proxmox, 2018-07-01 11:19:54 -0300
  LV Pool metadata       data_tmeta
  LV Pool data           data_tdata
  LV Status              available
  # open                 3
  LV Size                31.12 GiB
  Allocated pool data    5.20%
  Allocated metadata     0.10%
  Current LE             7967
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:4

  --- Logical volume ---
  LV Path                /dev/pve/vm-100-disk-1
  LV Name                vm-100-disk-1
  VG Name                pve
  LV UUID                n3OsjX-SFH7-E24T-KMAB-GQOV-NyeD-UAIk0K
  LV Write Access        read/write
  LV Creation host, time proxmox, 2018-07-01 12:09:40 -0300
  LV Pool name           data
  LV Status              available
  # open                 0
  LV Size                16.00 GiB
  Mapped size            0.00%
  Current LE             4096
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:6

  --- Logical volume ---
  LV Path                /dev/pve/vm-101-disk-2
  LV Name                vm-101-disk-2
  VG Name                pve
  LV UUID                0tcLvP-AFhG-hwma-bOsw-kfBr-73bA-YJ2ZiB
  LV Write Access        read/write
  LV Creation host, time proxmox, 2018-07-01 12:26:46 -0300
  LV Pool name           data
  LV Status              available
  # open                 0
  LV Size                32.00 GiB
  Mapped size            5.06%
  Current LE             8192
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:7

Everyone has a /dev/pve/* LV Path, but data doens't:

Code:
  --- Logical volume ---
  LV Name                data
  VG Name                pve
  LV UUID                J1k1cP-7xDS-Uisv-suim-CXMs-5FOM-lzoNp7
  LV Write Access        read/write
  LV Creation host, time proxmox, 2018-07-01 11:19:54 -0300
  LV Pool metadata       data_tmeta
  LV Pool data           data_tdata
  LV Status              available
  # open                 3
  LV Size                31.12 GiB
  Allocated pool data    5.20%
  Allocated metadata     0.10%
  Current LE             7967
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           253:4

I don't understand much about LVM, I know that local-lvm is this logical volume data that should be storing my VMs, but instead each VM create yet another logical volume. After all how is this structured? It's confusing for me.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!