[Solved] Update proxmox 7.2 : Error writing to file - write (28: No space left on device)

[jprcrna]

Hello,
We try to update our proxmox but we have a problem of space on the system.
We discover this problem of full space for the system because update do errors.
We make a apt autoclean and clean on the proxmox but the problem is still here.

We have 14.50go on this system. The proxmox work from 2016. Start with the 4.4 and make update until now. We are up to date the last time around end of june.

Can we earn place on the system? What can we do for this please ?

Here the log when we refresh the update by the web :


starting apt-get update
Hit:1 http://ftp.debian.org/debian bullseye InRelease
Get:2 http://security.debian.org bullseye-security InRelease [48.4 kB]
Err:2 http://security.debian.org bullseye-security InRelease
Error writing to file - write (28: No space left on device) [IP: 151.101.14.132 80]
Err:1 http://ftp.debian.org/debian bullseye InRelease
Splitting up /var/lib/apt/lists/ftp.debian.org_debian_dists_bullseye_InRelease into data and signature failed
Get:3 http://ftp.debian.org/debian bullseye-updates InRelease [44.1 kB]
Err:3 http://ftp.debian.org/debian bullseye-updates InRelease
Error writing to file - write (28: No space left on device) [IP: 199.232.138.132 80]
Hit:4 http://download.proxmox.com/debian/pve bullseye InRelease
Err:4 http://download.proxmox.com/debian/pve bullseye InRelease
Splitting up /var/lib/apt/lists/download.proxmox.com_debian_pve_dists_bullseye_InRelease into data and signature failed
Get:5 http://ftp.debian.org/debian bullseye-backports InRelease [49.0 kB]
Err:5 http://ftp.debian.org/debian bullseye-backports InRelease
Error writing to file - write (28: No space left on device) [IP: 199.232.138.132 80]
Reading package lists...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ftp.debian.org/debian bullseye InRelease: Splitting up /var/lib/apt/lists/ftp.debian.org_debian_dists_bullseye_InRelease into data and signature failed
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://download.proxmox.com/debian/pve bullseye InRelease: Splitting up /var/lib/apt/lists/download.proxmox.com_debian_pve_dists_bullseye_InRelease into data and signature failed
W: Failed to fetch http://ftp.debian.org/debian/dists/bullseye/InRelease Splitting up /var/lib/apt/lists/ftp.debian.org_debian_dists_bullseye_InRelease into data and signature failed
W: Failed to fetch http://security.debian.org/dists/bullseye-security/InRelease Error writing to file - write (28: No space left on device) [IP: 151.101.14.132 80]
W: Failed to fetch http://ftp.debian.org/debian/dists/bullseye-updates/InRelease Error writing to file - write (28: No space left on device) [IP: 199.232.138.132 80]
W: Failed to fetch http://ftp.debian.org/debian/dists/bullseye-backports/InRelease Error writing to file - write (28: No space left on device) [IP: 199.232.138.132 80]
W: Failed to fetch http://download.proxmox.com/debian/pve/dists/bullseye/InRelease Splitting up /var/lib/apt/lists/download.proxmox.com_debian_pve_dists_bullseye_InRelease into data and signature failed
W: Some index files failed to download. They have been ignored, or old ones used instead.
TASK OK



Thank you
(sorry for me english)

 

[jprcrna]

Ok when i upload an iso, the HD space of the proxmox system grow, when the upload crash, the space stay full

 

[Dunuin]

Try to delete old logs in /var/log, search for failed ISO uploads in /var/lib/vz and so on. There are also commands like find /var/ -type f -printf "%s %p\n" | sort -rn | head -n 20 to find the biggest files.

 

[jprcrna]

Ok thank you Dunuin, i try this roads now

 

[jprcrna]

Ok
nothing big in /var/log (350mo) and /var/lib/vz (370)
but with command find /var/ -type f -printf "%s %p\n" | sort -rn | head -n 20 we find big files for crash upload in /var/tmp/

files like this : pveupload-xxxxxxxxxxxxxxxxxxxx

big thank you Dunuin !
we can make update

before :
/dev/mapper/hyp2vg0-system 15G 14G 0 100% /
now :
/dev/mapper/hyp2vg0-system 15G 9,5G 4,3G 69% /

but with time our system with 14.5go is too small for big iso upload :

how can we do? can we resize easily ?
Oh ok we try to upload the iso with winscp on /srv/data/template/iso/ and it's work, but it's less pratical like this

 

[Dunuin]

14.5GB really isn't that much for the root filesystem. How to extend it really depends on the storage you are using (LVM/LVM-Thin/ZFS/btrfs/...). Usually, it's not that easy because shrinking partitions is always a bit problematic and you probably will have to shrink another partition to get some unallocated space to extend the root partition.

 

[jprcrna]

Yes, but it's the first configuration that our chief force to put in 2016.
We let the system like this for now
Thanks for your help Dunuin