PVE8.04: After upload of images temp file was not removed - filled up root filesystem

Glowsome

Renowned Member
Jul 25, 2017
173
44
68
51
The Netherlands
www.comsolve.nl
Conditions:

- PVE8.04 / latest
- iso/templates are mounted as a separate LVM volume under /data/iso ( seen as iso storage in PVE UI)
- logged in as federated OIDC user ( with Enterprise admin privileges)

Behavior experienced:
- Uploaded new iso to /data/iso
- iso was correctly added
- temp file in /var/tmp was NOT removed after transfer.
- templates were updated/downloaded
- temp file in /var/tmp was NOT removed after transfer.

This has resulted in filling up the root filesystem to 100% and making the box almost non-responsive until deleting these left-over files from /var/tmp

Questions are :
- in previous versions this has not been seen, so what has changed
- if this is an issue with rights as to the OIDC user (i know there are (still) limitations to such a user)
- is there a cleanup mechanism for "leftover" files starting with pveupload- in this directory ?

- Glowsome
 
mhmm i cannot really reproduce this here.

can you post

your exact versions (pveversion -v)
the permissions of the user you use to upload
and the full task log ?

thanks
 
Hello,

See below for output of pveversion -v

Code:
proxmox-ve: 8.0.2 (running kernel: 6.2.16-6-pve)
pve-manager: 8.0.4 (running version: 8.0.4/d258a813cfa6b390)
pve-kernel-6.2: 8.0.5
proxmox-kernel-helper: 8.0.3
pve-kernel-5.15: 7.4-4
proxmox-kernel-6.2.16-6-pve: 6.2.16-7
proxmox-kernel-6.2: 6.2.16-7
pve-kernel-6.2.16-5-pve: 6.2.16-6
pve-kernel-5.15.108-1-pve: 5.15.108-2
ceph-fuse: 16.2.11+ds-2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx3
ksmtuned: 4.20150326+b1
libjs-extjs: 7.0.0-3
libknet1: 1.25-pve1
libproxmox-acme-perl: 1.4.6
libproxmox-backup-qemu0: 1.4.0
libproxmox-rs-perl: 0.3.1
libpve-access-control: 8.0.4
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.0.7
libpve-guest-common-perl: 5.0.4
libpve-http-server-perl: 5.0.4
libpve-rs-perl: 0.8.5
libpve-storage-perl: 8.0.2
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve3
novnc-pve: 1.4.0-2
proxmox-backup-client: 3.0.2-1
proxmox-backup-file-restore: 3.0.2-1
proxmox-kernel-helper: 8.0.3
proxmox-mail-forward: 0.2.0
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.2
proxmox-widget-toolkit: 4.0.6
pve-cluster: 8.0.3
pve-container: 5.0.4
pve-docs: 8.0.4
pve-edk2-firmware: 3.20230228-4
pve-firewall: 5.0.3
pve-firmware: 3.7-1
pve-ha-manager: 4.0.2
pve-i18n: 3.0.5
pve-qemu-kvm: 8.0.2-4
pve-xtermjs: 4.16.0-3
qemu-server: 8.0.6
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.1.12-pve1

The user i use is authenticated over OIDC, and is member of the 'Administrators' -group.

Files being uploaded i see appearing in /var/tmp :
Code:
-rw------- 1 www-data www-data 704723592 Aug 16 12:05 pveupload-1c3b369b48a57761cf24973039acf79c

When i opened/started the post i had already cleaned out the files in there starting with pveupload-*

So to try and reproduce it uploading yet another ISO as we speak.
1692180657941.png

Well seems the ISO was too big, it filled up the filesystem, then the upload exited with an error, but the partial files were not cleaned .. so the filesystem remained full afterwards.

Is there no cleanup in place to - when this happens it frees up the partial (failed) upload ?
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!