Search results

I am not sure only counting things labelled as crash there is the relevant metric ;) every other open issue is either restore failing, or checkpoint failing, or some thing that is not yet supported but probably happens with real-world system containers..

yeah, like I said, the description is wrong ;)

that description is wrong - the name option uses the 'dns-name' format, which is defined here: https://git.proxmox.com/?p=pve-common.git;a=blob;f=src/PVE/JSONSchema.pm;h=115f811043360204c2ab07e86b8feb5278f2d594;hb=HEAD#l555

PVE 7 is EoL, please upgrade to the last released version of it (pve-container 4.4-5 should support bookworm containers) and then proceed with updating to 8.x

what version of PVE are you using? please post "pveversion -v" output in code tags!

rueckgaengig heisst in dem fall ja auch (vorher unbenutzten) block X schreiben, block X discarden.. oder bei filesystem, file X kopieren, kopie wieder loeschen. temp file X anlegen, wieder loeschen. alles dinge die je nach usage doch recht haeufig passieren koennen.. ich hab bei mir am NAS...

langfristig machts keinen unterschied sofern die hourly snapshots zeitnah wieder aufgeraeumt werden, aber fuer den transfer sehr wohl: transfer von A->D vs transfer von A->B->C->D , letzteres uebertraegt naemlich auch aenderungen in B die von C wieder rueckgaengig gemacht werden (oder in C die...

das kommt drauf an ob dass was die VM tut diese last rechtfertigt ;)

we don't have a build for those old versions.. what you could do is boot a Debian-12 live CD, install the client there and either backup the raw disk images, or mount the disks and backup the dir tree..

nein, replikation nimmt immer alle snapshots mit und das laesst sich auch nicht anders konfigurieren..

you are likely triggering an already fixed bug in ZFS: https://bugzilla.proxmox.com/show_bug.cgi?id=5288

wie kommst du darauf dass die last durch loopback verursacht wird? du musst im output noch eine vertikale linie dazudenken, die den "network" teil vom "tasks" teil trennt.. das eine VM CPU last erzeugt wenn sie was tut ist erstmal normal..

you either need pve-enterprise and a subscription, or pve-no-subscription (or pvetest ;)) enabled, else you won't get any updates for PVE itself..

so this zvol is "fat" (its full size is reserved up front), when you create a snapshot you need to have enough space available to allow fully overwriting the volume. you seem to not have enough space for that ;)

maybe your repository configuration is incomplete? see https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_package_repositories migration and shell access across node use the same SSH helper, so likely both was broken before between the new node and the old ones and you just didn't...

it can sometimes cause issues like this, yes. it's best to keep nodes at a similar version for this reason.

please upgrade pve01 and pve02 (or manually add pve03's host key to the legacy shared known hosts file).

please post the output of zfs list -o space,reservation,refreservation -r zfspool1/vm-101-disk-0

feel free to open a feature request on bugzilla.proxmox.com for this :)

I mean `proxmox-file-restore` which is used by the PVE file download feature. it would be possible to extend this with ACL support (for the tar case), but there is no such support at the moment. the FUSE mount also doesn't expose ACLs at the moment AFAICT. the catalog shell does allow...