Warning during PBS backup

L

lanepark5033

Member
Feb 20, 2025
42
4
8
I take warnings seriously, and try to correct them when they appear.
Below is a snippet of the backup log that ran last night and I need some help in understanding what I need to change to make the warnings go away.
Any help is appriciated...
 

Attachments

  • warninglog.png
    warninglog.png
    64.5 KB · Views: 17
That's normal when you over allocate (snapshots count too IIRC) with LVM-Thin. What's lvs -a look like? I don't recommend letting it auto extend. You cannot shrink it again and if something misbehaves you will just hit the 100% full issue a bit later. Either don't over allocate or keep an eye on the usage and do periodic trims. This isn't really PBS related, by the way.
 
Last edited:
  • Like
Reactions: news
Your data thin pool only has a real size of 13G~ but your virtual disks are proviisoned 34G~. You should generally not allocate more size that you have in total to a single disk. That doesn't really make sense as a single guest can fill it completely.
But right now only 54% of that pool is used so if you keep trimming and don't let the guest fill the pool it's fine.
Why is the pool so small? Can you share this too?
Bash: 
lsblk -o+FSTYPE,LABEL,MODEL
pvs
vgs
 
Last edited:
Here is what you asked for, I believe.
 

Attachments

  • vgdisplay.png
    vgdisplay.png
    41 KB · Views: 5
  • pvdisplay.png
    pvdisplay.png
    28.8 KB · Views: 5
  • lsblkWarning.png
    lsblkWarning.png
    82.6 KB · Views: 5
The data thin pool was created as a first attempt of installing proxmox, and was a default, at least as far as I recall.
Oh rats, I need to start over, in addition to the warning issues, I'm installing a second proxmox server and have been taking pictures from that GUI interface and need to redo all the photos on the failing server. My bad....
 
Last edited:
vgdisplay is not vgs. Something isn't adding up here. This system is called slightly different and the data pool is much larger. I also can't see a 202 guest.
 
Probably when I created 209 and 202 I did not create them in the ZFS and created them in local disk. They need to be reinstalled in the correct disk space. They were created recently.
 
What I'm saying is that your pictures appear to have been taken on different nodes.
 
You are absolutly correct, I fubared, and reinstalled both 202 and 209 into a ZFS disk that has far more space. Ran backups and the warning went away.

How do I close this as it needs to go away..... LOL
 
You must log in or register to reply here.
Top Bottom
Back