out of space

[toto-ets]

I was performing a backup of a vm, but then it stopped due to insufficient space on the disk, but now I can't free up space on the PBS because I don't see the backup of the vm that stopped halfway, where can I find the backup of the vm to delete it manually and free up space, in which path of the pbs?

 

[Chris]

You have to run garbage collection twice, separated by the configured cutoff time (default 24h 5min) to clean up unused chunks [0]. Since PS 3.4.0 you can reduce the cutoff time in the datastore tuning parameters [1] to not have to wait the default time period.

[0] https://pbs.proxmox.com/docs/maintenance.html#garbage-collection
[1] https://pbs.proxmox.com/docs/storage.html#tuning

 

[toto-ets]

if i run the command i get this error


TASK ERROR: atime safety check failed: update atime failed for chunk/file "/mnt/datastore/Datastore_PBS/.chunks/bb9f/bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8" - ENOSPC: No space left on device

 

[Chris]

if i run the command i get this error


TASK ERROR: atime safety check failed: update atime failed for chunk/file "/mnt/datastore/Datastore_PBS/.chunks/bb9f/bb9f8df61474d25e71fa00722318cd387396ca1736605e1248821cc0de3d3af8" - ENOSPC: No space left on device

Then you unfortunately will have to temporarily move some files or free up some space by removing files on the filesystem. Do you maybe have other content located on the same

 

[Indiana Horschd]

Hey,
I ran into the same issue "No space left on device".
Did you get it going again?
Unfortunately, I do not have any other content which I could delete.

CU
Indiana Horschd

 

[Impact]

Please share

lsblk -o+FSTYPE,LABEL,MODEL
df -hT

 

[Indiana Horschd]

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS FSTYPE     LABEL      MODEL
sda           8:0    0   9.1T  0 disk                                   WDC WUS721010ALE6L4
├─sda1        8:1    0   9.1T  0 part             zfs_member ZFS_Backup
└─sda9        8:9    0     8M  0 part
sdb           8:16   0   9.1T  0 disk                                   WDC WUS721010ALE6L4
├─sdb1        8:17   0   9.1T  0 part             zfs_member ZFS_Backup
└─sdb9        8:25   0     8M  0 part
sdc           8:32   0   9.1T  0 disk                                   WDC WUS721010ALE6L4
├─sdc1        8:33   0   9.1T  0 part             zfs_member ZFS_Backup
└─sdc9        8:41   0     8M  0 part
sdd           8:48   0   9.1T  0 disk                                   WDC WUS721010ALE6L4
├─sdd1        8:49   0   9.1T  0 part             zfs_member ZFS_Backup
└─sdd9        8:57   0     8M  0 part
nvme0n1     259:0    0 223.6G  0 disk                                   ATP NVMe M.2 2280 SSD
├─nvme0n1p1 259:1    0  1007K  0 part
├─nvme0n1p2 259:2    0     1G  0 part             vfat
└─nvme0n1p3 259:3    0 222.6G  0 part             zfs_member rpool

Filesystem       Type      Size  Used Avail Use% Mounted on
udev             devtmpfs   16G     0   16G   0% /dev
tmpfs            tmpfs     3.1G  1.8M  3.1G   1% /run
rpool/ROOT/pbs-1 zfs       216G  3.4G  212G   2% /
tmpfs            tmpfs      16G  8.1M   16G   1% /dev/shm
tmpfs            tmpfs     5.0M     0  5.0M   0% /run/lock
efivarfs         efivarfs  512K   83K  425K  17% /sys/firmware/efi/efivars
rpool            zfs       212G  128K  212G   1% /rpool
rpool/ROOT       zfs       212G  128K  212G   1% /rpool/ROOT
ZFS_Backup       zfs        27T   27T     0 100% /mnt/datastore/ZFS_Backup
tmpfs            tmpfs     3.1G     0  3.1G   0% /run/user/0

 

[Impact]

Since you use ZFS this is somewhat easy to prevent and fix.