Search results

1. please use code tags to post logs or config files.. 2. this is a bug that was fixed already, you need to upgrade PVE 8.x to a later version for it to be able to migrate to PVE 9.x

please provide the full task log and VM config. .sometimes there are bugs affecting migration compatibility. in general we try hard to make old->new and new->new work, new->old isn't always possible to support.

das ist ein problem auf Debian seite - fuer security updates werden die changelogs erst mit dem naechsten point release sichtbar. https://lists.debian.org/debian-security-announce/2026/msg00022.html

jein. der cache dient hautpsaechlich dazu, gewisse operationen schneller zu machen. beim backup wird schon (asynchron) auf den S3 storage gewartet - ein chunk/index/.. gilt erst als geschrieben wenn er im cache und im S3 abgelegt ist.

thanks! that seems very odd. can you run a zpool scrub using one of the kernel versions that boot?

the package in question hasn't been bumped yet, once it is the referenced bug will be updated. yes, the overload might very well be on the storage level. the log indicates that both pvestatd and the ha loops/cycles take way too long.

this part is already implemented on the PVE side, the VNETs are part of the ACL tree..

der "lokale" benchmark auf hetzner seite ist schon recht schlecht (der benchmark interagiert gar nicht mit dem storage, er testet nur den upload throughput!). vermutlich wirds in kombination mit der geringen bandbreite zwischen lokal und hetzner nicht besser - backup/restore/sync basieren auf...

check your reverse proxy and PVE access logs..

"not executable" could refer to the access mode (the executable bit) of a directory as well (see `man chmod`).

yes. for your system I am currently unsure what triggers it.

your system seems to be very overloaded, and there are log messages stating that the HA cycle took almost a minute right before the watchdog expires - since it's the HA stack that keeps the watchdog from expiring, I suspect this to be the cause on your system..

was there a backup running in the first case as well?

no, the 7TB is referring to the logical data before deduplication.. your file count is also a lot higher compared to your GC log, so something is very much fishy.. could you check your lifecycle rules to ensure that objects are not moved to some trash that still counts as deleted instead of...

could you post a GC task log?

the journal..

please provide the full logs preceding the unexpected reboot (at least the 10 minutes prior), as well as pveversion -v and the information whether the reboot happened during an upgrade. thanks!

are you running garbage collection as well (regularly?)?

netconsole or serial console are two commonly used options

Hi! you posted this in a German language thread. our forum only offers sections in German or English. please open a new thread in the English section.