Proxmox Proxmox Backup Server : Backup qui échouent à cause d'erreurs "Structure needs cleaning (os error 117)"

[MilesTEG]

Bonjour, j’a un souci avec un PBS qui m’affiche ceci :

Datastore: Proxmox-Backup

Garbage collection failed: update atime failed for chunk/file "/mnt/datastore/Proxmox-Backup/.chunks/b426/b4266a41a9373c840d3c6ef1a76b4396655d04e9adafcb2aeac84a4d2142c244" - EUCLEAN: Structure needs cleaning

Je ne sais pas du tout comment corriger le tir…

Sachant que ça , ça s’est bien passé :

 Job ID:       s-9fb7fb3c-317d
Datastore:    Proxmox-Backup

Pruning successful.

Mais que des sauvegardes depuis un mini pc vers le PBS plantent :

110: 2024-12-04 00:19:03 INFO: Starting Backup of VM 110 (qemu)
110: 2024-12-04 00:19:03 INFO: status = stopped
110: 2024-12-04 00:19:03 INFO: backup mode: stop
110: 2024-12-04 00:19:03 INFO: ionice priority: 7
110: 2024-12-04 00:19:03 INFO: VM Name: Docker-Firezone
110: 2024-12-04 00:19:03 INFO: include disk 'scsi0' 'local-lvm:vm-110-disk-1' 32G
110: 2024-12-04 00:19:03 INFO: include disk 'efidisk0' 'local-lvm:vm-110-disk-0' 4M
110: 2024-12-04 00:19:03 INFO: creating Proxmox Backup Server archive 'vm/110/2024-12-03T23:19:03Z'
110: 2024-12-04 00:19:03 INFO: starting kvm to execute backup task
110: 2024-12-04 00:19:04 INFO: started backup task '416e24de-feca-4605-90e7-c28cb83fd41c'
110: 2024-12-04 00:19:04 INFO: efidisk0: dirty-bitmap status: created new
110: 2024-12-04 00:19:04 INFO: scsi0: dirty-bitmap status: created new
110: 2024-12-04 00:19:07 INFO:  19% (6.2 GiB of 32.0 GiB) in 3s, read: 2.1 GiB/s, write: 0 B/s
110: 2024-12-04 00:19:10 INFO:  50% (16.2 GiB of 32.0 GiB) in 6s, read: 3.3 GiB/s, write: 0 B/s
110: 2024-12-04 00:19:13 INFO:  89% (28.8 GiB of 32.0 GiB) in 9s, read: 4.2 GiB/s, write: 0 B/s
110: 2024-12-04 00:19:14 INFO: 100% (32.0 GiB of 32.0 GiB) in 10s, read: 3.2 GiB/s, write: 0 B/s
110: 2024-12-04 00:19:14 ERROR: backup finish failed: command error: stat known chunks failed - stat failed on 8d1a9cb24e0d39c3854bf7b9cf06acc69100ea291b1737cc78dd12bfdc3f07c1
110: 2024-12-04 00:19:14 ERROR: 
110: 2024-12-04 00:19:14 ERROR: Caused by:
110: 2024-12-04 00:19:14 ERROR:     Structure needs cleaning (os error 117)
110: 2024-12-04 00:19:14 INFO: aborting backup job
110: 2024-12-04 00:19:14 INFO: stopping kvm after backup task
110: 2024-12-04 00:19:16 ERROR: Backup of VM 110 failed - backup finish failed: command error: stat known chunks failed - stat failed on 8d1a9cb24e0d39c3854bf7b9cf06acc69100ea291b1737cc78dd12bfdc3f07c1
110: 2024-12-04 00:19:16 ERROR: 
110: 2024-12-04 00:19:16 ERROR: Caused by:
110: 2024-12-04 00:19:16 ERROR:     Structure needs cleaning (os error 117)

La même raison : Structure needs cleaning


J'ai les mêmes erreurs affichées cette fois-ci par les tâches de backup des PVE sources :

vzdump 200 --notification-mode notification-system --quiet 1 --mode snapshot --fleecing 0 --storage PBS-VM-Asustor --notes-template '{{guestname}}'


200: 2024-12-04 12:00:07 INFO: Starting Backup of VM 200 (qemu)
200: 2024-12-04 12:00:07 INFO: status = running
200: 2024-12-04 12:00:07 INFO: VM Name: HAOS--NUC2
200: 2024-12-04 12:00:07 INFO: include disk 'scsi0' 'local-lvm:vm-200-disk-1' 32G
200: 2024-12-04 12:00:07 INFO: include disk 'efidisk0' 'local-lvm:vm-200-disk-0' 4M
200: 2024-12-04 12:00:07 INFO: backup mode: snapshot
200: 2024-12-04 12:00:07 INFO: ionice priority: 7
200: 2024-12-04 12:00:07 INFO: creating Proxmox Backup Server archive 'vm/200/2024-12-04T11:00:07Z'
200: 2024-12-04 12:00:07 INFO: issuing guest-agent 'fs-freeze' command
200: 2024-12-04 12:00:07 INFO: issuing guest-agent 'fs-thaw' command
200: 2024-12-04 12:00:07 INFO: started backup task '6920edd8-c294-4c15-9a3f-b4d8ee8031b5'
200: 2024-12-04 12:00:07 INFO: resuming VM again
200: 2024-12-04 12:00:07 INFO: efidisk0: dirty-bitmap status: existing bitmap was invalid and has been cleared
200: 2024-12-04 12:00:07 INFO: scsi0: dirty-bitmap status: existing bitmap was invalid and has been cleared
200: 2024-12-04 12:00:10 INFO:   1% (432.0 MiB of 32.0 GiB) in 3s, read: 144.0 MiB/s, write: 124.0 MiB/s
200: 2024-12-04 12:00:13 INFO:   3% (1.1 GiB of 32.0 GiB) in 6s, read: 214.7 MiB/s, write: 180.0 MiB/s
200: 2024-12-04 12:00:15 INFO:   3% (1.3 GiB of 32.0 GiB) in 8s, read: 112.0 MiB/s, write: 96.0 MiB/s
200: 2024-12-04 12:00:15 ERROR: backup write data failed: command error: write_data upload error: pipelined request failed: inserting chunk on store 'Proxmox-Backup' failed for c8b85eb75a876772e569938a7270ec07adc91cce8ca3f3ec73a7d0ee062c14db - Atomic rename failed for file "/mnt/datastore/Proxmox-Backup/.chunks/c8b8/c8b85eb75a876772e569938a7270ec07adc91cce8ca3f3ec73a7d0ee062c14db" - Structure needs cleaning (os error 117)
200: 2024-12-04 12:00:15 INFO: aborting backup job
200: 2024-12-04 12:00:15 INFO: resuming VM again
200: 2024-12-04 12:00:15 ERROR: Backup of VM 200 failed - backup write data failed: command error: write_data upload error: pipelined request failed: inserting chunk on store 'Proxmox-Backup' failed for c8b85eb75a876772e569938a7270ec07adc91cce8ca3f3ec73a7d0ee062c14db - Atomic rename failed for file "/mnt/datastore/Proxmox-Backup/.chunks/c8b8/c8b85eb75a876772e569938a7270ec07adc91cce8ca3f3ec73a7d0ee062c14db" - Structure needs cleaning (os error 117)

Dernière chose, ces mêmes PVE font des sauvegardes sans soucis sur un PBS distant (Layer7).

Du coup, comment je nettoie la structure ?

Ps : précision , le PBS est une VM sur un NAS Asustor dans VBox. Ça tournait super bien jusqu’à hier soir.
Sur ce PBS j’ai deux disques qui ne sont pas plein, loin de là.

Si l’un de vois pouvais m’aider je lui en serais très reconnaissant :jap:

Bonne journée