[SOLVED] Proxmox showing that my disk is full when it is not

GPGrieco · May 30, 2020

I noticed this issue when installing, but now the system is telling me it can't update because there is no available disk space so I really need to get it figured out. In the proxmox GUI under disks I can see all the disks plugged in, one of them is an SSD that I am using to host proxmox and the VMs, with other drives for data. Under disks if I click LVM it shows that the volume "pve" is 98% used (it is not but has showed that since everything was installed). Under LVM-Thin it shows 22% used. Why is this happening and how can I fix it?

Here are the output of some commands that might help:

fdisk -l

Code:

Disk /dev/sdc: 7.3 TiB, 8000450330624 bytes, 15625879552 sectors
Disk model: PERC H730 Mini 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: EDBA94BE-E5AE-4410-A289-7009CE904B49

Device     Start         End     Sectors  Size Type
/dev/sdc1   2048 15625877503 15625875456  7.3T Linux filesystem


Disk /dev/sda: 136.8 GiB, 146815733760 bytes, 286749480 sectors
Disk model: ST9146853SS     
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdb: 931.5 GiB, 1000207286272 bytes, 1953529856 sectors
Disk model: SanDisk SSD PLUS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: CBD99930-0EEE-4686-BDDF-98D573A16228

Device       Start        End    Sectors  Size Type
/dev/sdb1       34       2047       2014 1007K BIOS boot
/dev/sdb2     2048    1050623    1048576  512M EFI System
/dev/sdb3  1050624 1953529822 1952479199  931G Linux LVM


Disk /dev/mapper/pve-swap: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/pve-root: 96 GiB, 103079215104 bytes, 201326592 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/sdd: 2.7 TiB, 3000558944256 bytes, 5860466688 sectors
Disk model: Elements 25A1   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 5D22B7C1-95F2-489D-92FB-3D34D682A131

Device     Start        End    Sectors  Size Type
/dev/sdd1   2048 5860464639 5860462592  2.7T Microsoft basic data


Disk /dev/sde: 2.7 TiB, 3000558944256 bytes, 5860466688 sectors
Disk model: Elements 25A1   
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 348A7D31-3037-4F4F-B660-93953E6CB843

Device     Start        End    Sectors  Size Type
/dev/sde1     34      32767      32734   16M Microsoft reserved
/dev/sde2  32768 5860462591 5860429824  2.7T Microsoft basic data

Partition 1 does not start on physical sector boundary.




Disk /dev/mapper/pve-vm--100--disk--0: 32 GiB, 34359738368 bytes, 67108864 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: dos
Disk identifier: 0x9981a45b

Device                                 Boot   Start      End  Sectors  Size Id Type
/dev/mapper/pve-vm--100--disk--0-part1 *       2048  1050623  1048576  512M  b W95 FAT32
/dev/mapper/pve-vm--100--disk--0-part2      1052670 67106815 66054146 31.5G  5 Extended
/dev/mapper/pve-vm--100--disk--0-part5      1052672 67106815 66054144 31.5G 83 Linux

Partition 2 does not start on physical sector boundary.


Disk /dev/mapper/pve-vm--101--disk--0: 15 GiB, 16106127360 bytes, 31457280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 5D5D5137-B961-496D-B3FE-2EA7F3617522

Device                                 Start      End  Sectors Size Type
/dev/mapper/pve-vm--101--disk--0-part1  2048     4095     2048   1M BIOS boot
/dev/mapper/pve-vm--101--disk--0-part2  4096 31455231 31451136  15G Linux filesystem


Disk /dev/mapper/pve-vm--102--disk--0: 15 GiB, 16106127360 bytes, 31457280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: 5D5D5137-B961-496D-B3FE-2EA7F3617522

Device                                 Start      End  Sectors Size Type
/dev/mapper/pve-vm--102--disk--0-part1  2048     4095     2048   1M BIOS boot
/dev/mapper/pve-vm--102--disk--0-part2  4096 31455231 31451136  15G Linux filesystem


Disk /dev/mapper/pve-vm--103--disk--0: 5 GiB, 5368709120 bytes, 10485760 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: dos
Disk identifier: 0x90909090

Device                                 Boot Start      End  Sectors Size Id Type
/dev/mapper/pve-vm--103--disk--0-part1 *       64 10485758 10485695   5G a5 FreeBSD

Partition 1 does not start on physical sector boundary.


Disk /dev/mapper/pve-vm--104--disk--0: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: dos
Disk identifier: 0x418e7a17

Device                                 Boot   Start       End   Sectors  Size Id Type
/dev/mapper/pve-vm--104--disk--0-part1 *       2048   1187839   1185792  579M  7 HPFS/NTFS/exFAT
/dev/mapper/pve-vm--104--disk--0-part2      1187840 104855551 103667712 49.4G  7 HPFS/NTFS/exFAT


Disk /dev/mapper/pve-vm--105--disk--0: 136 GiB, 146028888064 bytes, 285212672 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: gpt
Disk identifier: DF5EBD32-70CD-4DA7-BF17-E2EDBE1A039E

Device                                 Start       End   Sectors  Size Type
/dev/mapper/pve-vm--105--disk--0-part1  2048      4095      2048    1M BIOS boot
/dev/mapper/pve-vm--105--disk--0-part2  4096 285210623 285206528  136G Linux filesystem


Disk /dev/mapper/pve-vm--108--disk--0: 20 GiB, 21474836480 bytes, 41943040 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: dos
Disk identifier: 0xfd483ef2

Device                                 Boot   Start      End  Sectors Size Id Type
/dev/mapper/pve-vm--108--disk--0-part1 *       2048  2099199  2097152   1G 83 Linux
/dev/mapper/pve-vm--108--disk--0-part2      2099200 41943039 39843840  19G 8e Linux LVM


Disk /dev/mapper/pve-vm--106--disk--0: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes
Disklabel type: dos
Disk identifier: 0x69592e95

Device                                 Boot Start      End  Sectors Size Id Type
/dev/mapper/pve-vm--106--disk--0-part1 *     2048 20969471 20967424  10G 83 Linux


Disk /dev/mapper/pve-vm--110--disk--0: 8 GiB, 8589934592 bytes, 16777216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 65536 bytes / 65536 bytes


Disk /dev/mapper/drive2-vm--104--disk--0: 136 GiB, 146028888064 bytes, 285212672 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: DF5EBD32-70CD-4DA7-BF17-E2EDBE1A039E

Device                                    Start       End   Sectors  Size Type
/dev/mapper/drive2-vm--104--disk--0-part1  2048      4095      2048    1M BIOS boot
/dev/mapper/drive2-vm--104--disk--0-part2  4096 285210623 285206528  136G Linux filesystem

vgs:

Code:

  VG     #PV #LV #SN Attr   VSize   VFree 
  drive2   1   1   0 wz--n- 136.73g 748.00m
  pve      1  12   0 wz--n- 931.01g  15.99g

lvs:

Code:

  LV            VG     Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  vm-104-disk-0 drive2 -wi-a----- 136.00g                                                   
  data          pve    twi-aotz-- 794.79g             21.52  1.27                           
  root          pve    -wi-ao----  96.00g                                                   
  swap          pve    -wi-ao----   8.00g                                                   
  vm-100-disk-0 pve    Vwi-a-tz--  32.00g data        32.01                                 
  vm-101-disk-0 pve    Vwi-a-tz--  15.00g data        18.27                                 
  vm-102-disk-0 pve    Vwi-a-tz--  15.00g data        18.27                                 
  vm-103-disk-0 pve    Vwi-a-tz--   5.00g data        22.28                                 
  vm-104-disk-0 pve    Vwi-a-tz--  50.00g data        38.39                                 
  vm-105-disk-0 pve    Vwi-aotz-- 136.00g data        89.25                                 
  vm-106-disk-0 pve    Vwi-aotz--  10.00g data        98.20                                 
  vm-108-disk-0 pve    Vwi-a-tz--  20.00g data        14.67                                 
  vm-110-disk-0 pve    Vwi-a-tz--   8.00g data        10.73

ermanishchawla · May 30, 2020

what is space left in root partition, it is referring that

GPGrieco · May 30, 2020

df:

Code:

Filesystem            1K-blocks      Used  Available Use% Mounted on
udev                   16394196         0   16394196   0% /dev
tmpfs                   3283760     26864    3256896   1% /run
/dev/mapper/pve-root   98559220  97801152          0 100% /
tmpfs                  16418788     40560   16378228   1% /dev/shm
tmpfs                      5120         0       5120   0% /run/lock
tmpfs                  16418788         0   16418788   0% /sys/fs/cgroup
/dev/sdc1            7750287860 678529424 6681095168  10% /mnt/storage
/dev/fuse                 30720        20      30700   1% /etc/pve
tmpfs                   3283756         0    3283756   0% /run/user/0

It says 0 available. This is wrong though because it has said that since it was a fresh install.

ermanishchawla · May 30, 2020

GPGrieco said:

df:

Code:

Filesystem            1K-blocks      Used  Available Use% Mounted on
udev                   16394196         0   16394196   0% /dev
tmpfs                   3283760     26864    3256896   1% /run
/dev/mapper/pve-root   98559220  97801152          0 100% /
tmpfs                  16418788     40560   16378228   1% /dev/shm
tmpfs                      5120         0       5120   0% /run/lock
tmpfs                  16418788         0   16418788   0% /sys/fs/cgroup
/dev/sdc1            7750287860 678529424 6681095168  10% /mnt/storage
/dev/fuse                 30720        20      30700   1% /etc/pve
tmpfs                   3283756         0    3283756   0% /run/user/0

It says 0 available. This is wrong though because it has said that since it was a fresh install.

just do the following

du -shc /var/lib/vz

GPGrieco · May 30, 2020

Code:

19G     /var/lib/vz
19G     total

This what I got back

ermanishchawla · May 30, 2020

GPGrieco said:
Code:

19G /var/lib/vz 19G total

This what I got back

Check which file is grown beyond size,

du -shc /
will tell u that and you can delete unwanted files

GPGrieco · May 30, 2020

Code:

du: cannot access '/proc/5990/task/5990/fd/3': No such file or directory
du: cannot access '/proc/5990/task/5990/fdinfo/3': No such file or directory
du: cannot access '/proc/5990/fd/4': No such file or directory
du: cannot access '/proc/5990/fdinfo/4': No such file or directory
741G    /
741G    total

There is a backup drive that isn't in the server right now so that could be the errors there.

ermanishchawla · May 30, 2020

GPGrieco said:
Code:

du: cannot access '/proc/5990/task/5990/fd/3': No such file or directory du: cannot access '/proc/5990/task/5990/fdinfo/3': No such file or directory du: cannot access '/proc/5990/fd/4': No such file or directory du: cannot access '/proc/5990/fdinfo/4': No such file or directory 741G / 741G total

There is a backup drive that isn't in the server right now so that could be the errors there.

There is something sitting please review the output of previous command and see files which are of big size and delete them

malnaim · May 30, 2020

Could you check if there are ISO and templates files by default they are stored in local (this is the root partition) not local-lvm

GPGrieco · May 30, 2020

ermanishchawla said:
There is something sitting please review the output of previous command and see files which are of big size and delete them

That was the output of the command you gave.

malnaim said:
Could you check if there are ISO and templates files by default they are stored in local (this is the root partition) not local-lvm

That is exactly what happened. Thank you!

Search

Search

[SOLVED] Proxmox showing that my disk is full when it is not

GPGrieco

New Member

ermanishchawla

Well-Known Member

GPGrieco

New Member

ermanishchawla

Well-Known Member

GPGrieco

New Member

ermanishchawla

Well-Known Member

GPGrieco

New Member

ermanishchawla

Well-Known Member

malnaim

Member

GPGrieco

New Member