That is because during sync, already known chunks (since 4.1 limited to the same group, see [0]) can be skipped. These might however not be good anymore locally, needing a re-verification.
[0]...
ah, thanks for the pointer, i searched bugzilla but did miss this ticket.
but for my curiousity - when newly pulled data chunks are already verified - why do they appear unverified at the sync target when they had not been verified at the source...
hi, as it seems syncing a datastore to another pbs will "inherit" the verify state of the source snapshot(s)
is there a way to unset that verified flag on/after transfer so verify can be run AFTER transfer/sync, so we can verify freshly...
This chunk is the all zero unencrypted but compressed chunk. We use it for the atime update safety check on garbage collection, it being inserted if not present. You might disable the atime safety check (in the datastore tuning options) if you...
to shed some further light into the internals of PBS: blobs are never referencing chunks. blobs and chunks are the same thing format-wise, just used for different purposes:
- chunk: blob stored in the chunk store, to be referenced by indices via...
i have made some weird observation, i cannot explain to myself
i switched my repos to encrypted a while ago and all unencrypted backups have been purged and removed by garbage collection.
in webui all backup snapshots show up encrypted.
for...
Hi Roland, i appreciate the interest - i thought that's what i was doing here, reporting it, tbh?
thanks for the link, i thought i remember seeing that bug report, and the purple links for the attachments confirmed it :) i couldn't be sure if it...
>i thought that's what i was doing here, reporting it, tbh
yes, thanks, but for a bug to be reproduced (which helps a lot resolving it), a "receipe" (i.e. detailed description of setup and what to do) is needed.
so if you can provide such, i'm...
there is a bugticket on something hugepage related at https://bugzilla.proxmox.com/show_bug.cgi?id=7052
i you have a reproducer for a hugepage issue, i'm sure it would be worth reporting it
not sure if this is a result of the upgrade and how it looked before - but is this normal/intentional that size and encryption staatus for client.log.blob is not shown and that both blob files are not downloadable ? when unencrypted, they can be...
you may try new verification reads and workers options, it considerably improves verification speed, from a first test i see 2-3x better performance - which is equivalent to the findings reported at...
you may try new verification reads and workers options, it considerably improves verification speed, from a first test i see 2-3x better performance - which is equivalent to the findings reported at...
We're pleased to announce the release of Proxmox Backup Server 4.1.
This version is based on Debian 13.2 (“Trixie”), uses Linux kernel 6.17.2-1 as the new stable default, and comes with ZFS 2.3.4 for reliable, enterprise-grade storage and...
No, we do not belittle this at all, and we do not delay this for time reason, the current system with having an ESP on every mirror device in addition of being able to recreate it is simply safe and redundant enough for the practical cases that...
yes, raid won't make backup obsolete.
but from my admin perspective, it would be logical consequence to regularly check/scrub 100% of your system disks and not only 99% (i.e. 100% minus boot-part minus efi-part) , even if it would be possible to...
In general, it would be also good to note that the ESP itself is not really stateful and can be rebuilt from scratch relatively easily, e.g. using a PVE ISO's debug shell to do so. After all there are mainly the kernel and initrd's located on...
>afaik, i/o errors typically happen on read, not on write.
addon note for this:
https://www.enterprisestorageforum.com/hardware/drive-reliability-studies/
"The authors found that final read errors (read errors after multiple retries) are about...