sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 120G 0 disk
├─sda1 8:1 0 243M 0 part /boot
├─sda2 8:2 0 1K 0 part
└─sda5 8:5 0 15.8G 0 part
├─debian--vg-root 254:0 0 14.8G 0 lvm /
└─debian--vg-swap_1 254:1 0 1G 0 lvm [SWAP]
sr0 11:0 1 1024M 0 rom
________________________________________
sudo parted /dev/sda
GNU Parted 3.2
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: QEMU QEMU HARDDISK (scsi)
Disk /dev/sda: 129GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 256MB 255MB primary ext2 boot
2 257MB 17.2GB 16.9GB extended
5 257MB 17.2GB 16.9GB logical lvm
HDD size for this VM is set t o120GB.
Proxmox 4.3 with simple local ext4 disk as a storage, but the same situation is on 5.3 with lvm-thin dedicated disk.
Where did 129GB came from? Is this a bug?
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 120G 0 disk
├─sda1 8:1 0 243M 0 part /boot
├─sda2 8:2 0 1K 0 part
└─sda5 8:5 0 15.8G 0 part
├─debian--vg-root 254:0 0 14.8G 0 lvm /
└─debian--vg-swap_1 254:1 0 1G 0 lvm [SWAP]
sr0 11:0 1 1024M 0 rom
________________________________________
sudo parted /dev/sda
GNU Parted 3.2
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
Model: QEMU QEMU HARDDISK (scsi)
Disk /dev/sda: 129GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 256MB 255MB primary ext2 boot
2 257MB 17.2GB 16.9GB extended
5 257MB 17.2GB 16.9GB logical lvm
HDD size for this VM is set t o120GB.
Proxmox 4.3 with simple local ext4 disk as a storage, but the same situation is on 5.3 with lvm-thin dedicated disk.
Where did 129GB came from? Is this a bug?