[SOLVED] Local storage /dev/mapper/pve-root full

M

marin

Member
Mar 17, 2023
5
0
6
Hello,

My local storage is 98% full and I can not figure out why. The FS size is 100G

My PVE version is 7.2-3

df -h

Code: 
Filesystem            Size  Used Avail Use% Mounted on
udev                   32G     0   32G   0% /dev
tmpfs                 6.3G  2.2M  6.3G   1% /run
/dev/mapper/pve-root   94G   88G  2.0G  98% /
tmpfs                  32G   46M   32G   1% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
/dev/fuse             128M   16K  128M   1% /etc/pve
tmpfs                 6.3G     0  6.3G   0% /run/user/0

du -smh /*

Code: 
0       /bin
92M     /boot
46M     /dev
4.8M    /etc
4.0K    /home
0       /lib
0       /lib32
0       /lib64
0       /libx32
16K     /lost+found
4.0K    /media
83G     /mnt
4.0K    /opt
du: cannot access '/proc/3433/task/3433/fd/4': No such file or directory
du: cannot access '/proc/3433/task/3433/fdinfo/4': No such file or directory
du: cannot access '/proc/3433/fd/3': No such file or directory
du: cannot access '/proc/3433/fdinfo/3': No such file or directory
0       /proc
5.6M    /root
2.2M    /run
0       /sbin
4.0K    /srv
0       /sys
40K     /tmp
2.3G    /usr
2.3G    /var

I looked at /var/logs, cleared everything. There are no ISO files uploaded. I can not figure out what is taking so much space.
 
For others who will come across this later:

I suspect you marked it solved because you found that /mnt at 83G is the culprit due to data being located in root volume, rather than a disk which you thought was mounted?

Its always best to run "du" with -x option, that way it wont cross filesystem boundaries and will give you an accurate information about the specific parent mountpoint.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
bbgeek17 said:
For others who will come across this later:

I suspect you marked it solved because you found that /mnt at 83G is the culprit due to data being located in root volume, rather than a disk which you thought was mounted?

Its always best to run "du" with -x option, that way it wont cross filesystem boundaries and will give you an accurate information about the specific parent mountpoint.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
Yes that's correct. I just missed that it was in root volume :)
 
Hi, I´m facing the same issue with pve-root taking a lot of space but no luck finding why:


Code: 
# lsblk

NAME                         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
nvme0n1                      259:0    0 953.9G  0 disk
├─nvme0n1p1                  259:1    0  1007K  0 part
├─nvme0n1p2                  259:2    0     1G  0 part /boot/efi
└─nvme0n1p3                  259:3    0 952.9G  0 part
  ├─pve-swap                 252:0    0     8G  0 lvm  [SWAP]
  ├─pve-root                 252:1    0    96G  0 lvm  /
  ├─pve-data_tmeta           252:2    0     8G  0 lvm
  │ └─pve-data-tpool         252:4    0   688G  0 lvm
  │   ├─pve-data             252:5    0   688G  1 lvm
  │   ├─pve-vm--200--disk--0 252:7    0    64G  0 lvm
  │   ├─pve-vm--104--disk--0 252:8    0    64G  0 lvm
  │   ├─pve-vm--105--disk--0 252:9    0     8G  0 lvm
  │   ├─pve-vm--110--disk--0 252:10   0     8G  0 lvm
  │   └─pve-vm--108--disk--1 252:11   0    64G  0 lvm
  ├─pve-data_tdata           252:3    0   688G  0 lvm
  │ └─pve-data-tpool         252:4    0   688G  0 lvm
  │   ├─pve-data             252:5    0   688G  1 lvm
  │   ├─pve-vm--200--disk--0 252:7    0    64G  0 lvm
  │   ├─pve-vm--104--disk--0 252:8    0    64G  0 lvm
  │   ├─pve-vm--105--disk--0 252:9    0     8G  0 lvm
  │   ├─pve-vm--110--disk--0 252:10   0     8G  0 lvm
  │   └─pve-vm--108--disk--1 252:11   0    64G  0 lvm
  └─pve-shared--zfs          252:6    0   128G  0 lvm


Code: 
# df -h

Filesystem                             Size  Used Avail Use% Mounted on
udev                                    16G     0   16G   0% /dev
tmpfs                                  3.1G  2.5M  3.1G   1% /run
/dev/mapper/pve-root                    94G   85G  9.0G  91% /
tmpfs                                   16G   69M   16G   1% /dev/shm
tmpfs                                  5.0M     0  5.0M   0% /run/lock
efivarfs                               128K   31K   93K  25% /sys/firmware/efi/efivars
/dev/nvme0n1p2                        1022M   12M 1011M   2% /boot/efi
tank                                   121G  128K  121G   1% /tank
tank/subvol-101-disk-0                 8.0G  759M  7.3G  10% /tank/subvol-101-disk-0
tank/subvol-109-disk-0                  16G  1.3G   15G   9% /tank/subvol-109-disk-0
tank/subvol-102-disk-0                  16G  487M   16G   3% /tank/subvol-102-disk-0
tank/subvol-107-disk-0                 2.0G  271M  1.8G  14% /tank/subvol-107-disk-0
/dev/fuse                              128M   56K  128M   1% /etc/pve
192.168.3.1:/volume2/media/multimedia   14T   11T  3.7T  74% /mnt/media
192.168.3.1:/volume1/bitcoin            14T  8.1T  5.9T  58% /mnt/bitcoin
192.168.3.1:/volume1/proxmox            14T  8.1T  5.9T  58% /mnt/pve/nas
tmpfs                                  3.1G     0  3.1G   0% /run/user/0

Code: 
# du -hs /var/lib/vz/*

17G     /var/lib/vz/dump
4.0K    /var/lib/vz/images
4.0K    /var/lib/vz/import
4.0K    /var/lib/vz/private
4.0K    /var/lib/vz/snippets
259M    /var/lib/vz/template

Code: 
# du -smhx /*

0       /bin
415M    /boot
0       /dev
9.1M    /etc
20K     /home
0       /lib
0       /lib64
16K     /lost+found
4.0K    /media
12K     /mnt
4.0K    /opt
du: cannot access '/proc/21071': No such file or directory
du: cannot access '/proc/21646': No such file or directory
du: cannot access '/proc/21648/task/21648/fd/4': No such file or directory
du: cannot access '/proc/21648/task/21648/fdinfo/4': No such file or directory
du: cannot access '/proc/21648/fd/3': No such file or directory
du: cannot access '/proc/21648/fdinfo/3': No such file or directory
0       /proc
30M     /root
2.6M    /run
0       /sbin
4.0K    /srv
0       /sys
512     /tank
44K     /tmp
4.9G    /usr
18G     /var
 
Last edited:
isc30 said:
Hi, I´m facing the same issue with pve-root taking a lot of space but no luck finding why:
Click to expand...
isc30 said:
Running `umount /mnt/*` and then `du -smhx /*` showed hidden files.
Click to expand...
The reason you did not see the "hidden" files in your "du" runs is because you had "-x" option. That tells "du" to not cross filesystem boundaries.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
You must log in or register to reply here.
Top Bottom