Hi,
currently only the change detection mode set to metadata produces these outputs. Might be worth to show this information for other modes as well, e.g. guarded by a summary flag. Feel free to open an enhancement request in our bugzilla for this.
apparently, my question was a little bit too early
when switching to metadata for change detection, it now prints file information
i'm really impressed that proxmox-backup-client does an incremental run across 336254 and 106956 dirs in just...
war/ist es ihnen doch auch!?
https://docs.docker.com/engine/release-notes/29/
Breaking Changes
The daemon now requires API version v1.44 or later (Docker v25.0+).
aber was können die denn dafür, daß deren "konsumenten" pennen oder leute ggf...
is there a way to also have shown the number of processed files instead of volume/gb ?
i'm doing some runtime testing for backups with larger file count and i cannot estimate based on this information
i know i can set PBS_LOG=debug, but i'm...
ich weiss nicht ob ich das "hürden einbauen" nennen mag. wenn von programmen/tools APIs geändert werden , hat das einen grund. davon abgesehen gibt es ja offensichtlich die möglichkeit clientseitig die gewünschte api version mitzuteilen bzw. zu...
Das verstehe ich nicht. Die reguläre Backupfunktion von ProxmoxVE (vzdump mit vma-Archiven) kann immer nur full-Backups, egal ob vms oder lxcs. Der PBS macht dagegen immer ein Full- und inkrementelles Backup, egal ob Dateien, vms oder lxcs.
Ich...
>Das ist doch gar nicht der Punkt. Ich finde es völlig legitim, docker in lxcs zu benutzen, wenn man sich der Problematik bewusst ist und den
>damit verbundenen Folgen (Ausfall von Diensten, troubleshooting etc) leben kann. Mein Eindruck ist...
Also meine VM mit den Docker Containern ist gar nicht so verschwenderisch auf dem kleinen Atom Prozessor. Wenn der kleine Kernel zu viel ist, dann ist die Kiste etwas knapp bemessen. Warum soll ich eigentlich nur inkrementelle Backups vom LXC...
i don't see performance regression . it's performance disadvantages of qcow2 on top of zfs are greatly exaggerated, imho.
qcow2:
# dd if=/dev/zero of=/dev/sdb bs=1024k status=progress count=10240
9954131968 bytes (10 GB, 9.3 GiB) copied, 12...
this is not meant to to make users/customers uncertain about product quality , but whoever is deeper into using qcow2 may have a look at https://bugzilla.proxmox.com/show_bug.cgi?id=7012 , it's about a case where qcow2 performs pathologically...
Just an update. This was narrowed down to the Nimble box not supporting some newer functions.
BLKZEROOUT to be exact.
Disabling detect-zeroes=on is our work around until Nimble provides the permanent fix. This issue is solved!
Proxmox...
Hi,
a large part of that is feature requests and that is not a bad thing in itself. Many things are easy to request, but a lot of effort to actually implement. There's a wide variety of uses cases and wishes.
If they really are outdated, feel...
so i disabled ( removed) net 1 from broken server
and the problem is gone, :)
no more hiccups ... performance is a bit on the low side, but no full hiccups here ,
so i reinstated net 1 , and the problem returned
this is how it looks when...
i would first disable net1 temporarly in the old and then provide 4 cores and 2048mb to the new lxc
comparing two different operating systems is hard enough - but they should have the same lxc/hardware ressources
i guess the most prominent...
you mean you have a second lxc container which works without problems?
those are both turnkey linux lxc containers, or what?
the one with the issue has docker inside?
we had a ticket for this at https://bugzilla.proxmox.com/show_bug.cgi?id=3118, which i just closed.
if anybody still sees this with any recent linux distro, please report. (i guess this exists, as bugs constantly (re)appear in linux) ;)