[SOLVED] LOCAL STORAGE SPACE FULL

[Atenea.Ing]

Hello.
i am working with proxmox recently. At my work there was already a proxmox server running, and the local space is full, is there a way to expand it? already has two new solid disk installed.
Thank you so much

 

[Dunuin]

Not enough info.
What do you mean wih "local space"? The "local" storage? Then you would need to:
A.) find out whats filling up your root filesystem and stop it or
B.) expand your root filesystem
No info about used filesystems.

Outputs like lsblk, zpool list -v, zfs list -o space, lvs, vgs, cat /etc/pve/storage.cfg, df -h, du -a /var | sort -n -r | head -n 20 could help.

 

[Atenea.Ing]

I would like to know how to expand local storage.

execute lsblk:

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 447.1G 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 512M 0 part /boot/efi
└─sda3 8:3 0 446.6G 0 part
├─pve-swap 253:0 0 8G 0 lvm [SWAP]
├─pve-root 253:1 0 96G 0 lvm /
├─pve-data_tmeta 253:2 0 3.3G 0 lvm
│ └─pve-data-tpool 253:6 0 320.1G 0 lvm
│ ├─pve-data 253:7 0 320.1G 1 lvm
│ ├─pve-vm--100--disk--0 253:8 0 20G 0 lvm
│ ├─pve-vm--101--disk--0 253:9 0 50G 0 lvm
│ ├─pve-vm--102--disk--0 253:10 0 50G 0 lvm
│ ├─pve-vm--104--disk--0 253:11 0 200G 0 lvm
│ ├─pve-vm--106--disk--0 253:12 0 100G 0 lvm
│ └─pve-vm--110--disk--0 253:13 0 50G 0 lvm
└─pve-data_tdata 253:3 0 320.1G 0 lvm
└─pve-data-tpool 253:6 0 320.1G 0 lvm
├─pve-data 253:7 0 320.1G 1 lvm
├─pve-vm--100--disk--0 253:8 0 20G 0 lvm
├─pve-vm--101--disk--0 253:9 0 50G 0 lvm
├─pve-vm--102--disk--0 253:10 0 50G 0 lvm
├─pve-vm--104--disk--0 253:11 0 200G 0 lvm
├─pve-vm--106--disk--0 253:12 0 100G 0 lvm
└─pve-vm--110--disk--0 253:13 0 50G 0 lvm
sdb 8:16 0 931.5G 0 disk
├─atenea--lvm-atenea--lvm_tmeta 253:4 0 9.3G 0 lvm
│ └─atenea--lvm-atenea--lvm-tpool 253:14 0 912.8G 0 lvm
│ ├─atenea--lvm-atenea--lvm 253:15 0 912.8G 1 lvm
│ ├─atenea--lvm-vm--105--disk--0 253:16 0 240G 0 lvm
│ ├─atenea--lvm-vm--108--disk--0 253:17 0 250G 0 lvm
│ ├─atenea--lvm-vm--103--disk--0 253:18 0 160G 0 lvm
│ ├─atenea--lvm-vm--110--disk--0 253:19 0 50G 0 lvm
│ └─atenea--lvm-vm--109--disk--0 253:20 0 1.9T 0 lvm
└─atenea--lvm-atenea--lvm_tdata 253:5 0 912.8G 0 lvm
└─atenea--lvm-atenea--lvm-tpool 253:14 0 912.8G 0 lvm
├─atenea--lvm-atenea--lvm 253:15 0 912.8G 1 lvm
├─atenea--lvm-vm--105--disk--0 253:16 0 240G 0 lvm
├─atenea--lvm-vm--108--disk--0 253:17 0 250G 0 lvm
├─atenea--lvm-vm--103--disk--0 253:18 0 160G 0 lvm
├─atenea--lvm-vm--110--disk--0 253:19 0 50G 0 lvm
└─atenea--lvm-vm--109--disk--0 253:20 0 1.9T 0 lvm
sdc 8:32 0 1.7T 0 disk
├─sdc1 8:33 0 1.2T 0 part
└─sdc2 8:34 0 577.8G 0 part
sdd 8:48 0 1.7T 0 disk


execute lvs:

LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
atenea-lvm atenea-lvm twi-aotz-- 912.76g 44.75 2.34
snap_vm-105-disk-0_vzdump atenea-lvm Vri---tz-k 240.00g atenea-lvm vm-105-disk-0
vm-103-disk-0 atenea-lvm Vwi-aotz-- 160.00g atenea-lvm 44.77
vm-105-disk-0 atenea-lvm Vwi-a-tz-- 240.00g atenea-lvm 50.28
vm-108-disk-0 atenea-lvm Vwi-a-tz-- 250.00g atenea-lvm 35.69
vm-109-disk-0 atenea-lvm Vwi-a-tz-- <1.86t atenea-lvm 4.04
vm-110-disk-0 atenea-lvm Vwi-aotz-- 50.00g atenea-lvm 100.00
data pve twi-aotz-- <320.10g 94.75 5.13
root pve -wi-ao---- 96.00g
snap_vm-100-disk-0_vzdump pve Vri---tz-k 20.00g data vm-100-disk-0
swap pve -wi-ao---- 8.00g
vm-100-disk-0 pve Vwi-a-tz-- 20.00g data 77.61
vm-101-disk-0 pve Vwi-aotz-- 50.00g data 65.08
vm-102-disk-0 pve Vwi-aotz-- 50.00g data 97.94
vm-104-disk-0 pve Vwi-aotz-- 200.00g data 55.62
vm-106-disk-0 pve Vwi-aotz-- 100.00g data 44.59
vm-110-disk-0 pve Vwi-a-tz-- 50.00g data 100.00


I am new in this, I am learnig.
I appreciate all the information you can share with me.

 

[Atenea.Ing]

al the vm and the ct are located in atenea-lvm

 

[Dunuin]

al the vm and the ct are located in atenea-lvm

No, a lot of VMs/LXCs are stored on your system disks LVM-Thin pool in "local-lvm".

Your "local" storage should be big enough with its 100GiB unless you store lots of ISOs or backups there.
In case those are ISOs, I would delete some, as you usually don't need them anymore after installing a VM (just make sure to remove the ISO from the VMs virtual CD drive first).
In case you store your backups there, this would be bad practice as you are storing VMs/LXCs on the same disk and you should think about buying a dedicated disk for backups.
Or it isn't caused by ISO/backups on "local" and you screwed something up, filling up your root filesystem.
Like writing data to an non-mounted mountpoint or never having a look at the system log to identify problems that are spamming the logs.

I would recommend first to find out what files are filling up your root filesystem.

 

[Atenea.Ing]

yes, it has de backups in the same disk, Could you pleas tell me how do I configure a new disk to be the backup?

 

[Dunuin]

Easiest would be to format an empty disk as a "directory" storage and setting the content type to "VZDump backups". You find that in your webUI at YourNode -> Disks -> Directory -> Create.

Way better than VZDump would be getting a (or better two with one offsite) dedicated machine running PBS (Proxmox Backup Server).

 

[Atenea.Ing]

Could you please tell me how can i format as a "directory" storage. I don´t find that option.

 

[Dunuin]

 

[Atenea.Ing]

You are amazing!!!! Thank you so much. I resolve my problem. All the backups were in my local. I really appreciate your help, really thank you very much, i am new in this, and i´m learning yet.