Backup failed, inodes still in use

mcdowellster

Active Member
Jun 13, 2018
31
4
28
39
Hello,

I have a large raw disk I backup to a usb disk mounted. The backup failed as I hadn't cleaned up the old backup first which tends to happen a few times a month. The failure happens when the disk runs out of space. Typically once it fails the used temp space is cleaned up and the inodes are freed. I delete an old backup and start it again. No issues.

This time the backup failed, the mount broke so I had to reboot the box. I get back into the OS, the disk shows full. The inodes are 100% in use but there are only 600GB of files on a 8GTB disk.

/dev/sdh2 7813894144 7811710976 2183168 100%

Where does proxmox write temp data during the backup process? I can't seem to find anything eating these inodes.
 
File system version 1.0
Sector size 512 bytes
Cluster size 2 MB
Volume size 7452 GB
Used space 7450 GB
Available space 2138 MB
Totally 9 directories and 32 files.

The mount doesn't add up to this at all...

DU shows the root of the mount using most of the space... there are no visible files.
du /eclipseUSB | sort -rh
614985728 /eUSB
483143680 /eUSB/dump
99733504 /eSB/images
32100352 /eUSB/template
31891456 /eUSB/template/iso
206848 /eUSB/template/cache
6144 /eUSB/private
2048 /eUSB/private/iso
2048 /eUSB/private/cache
2048 /eUSB/images/115
 
Backed up my backups (lol) and created a new filesystem for the disk to resolve.

Not sure why but my disk was formatted with exfat which isn't really a good choice.
 

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!