Recent content by RolandK

apt install python3-pylibacl ?

ok. thanks for making it clear

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 downloaded

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 https://bugzilla.proxmox.com/show_bug.cgi?id=5035#c2

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 https://bugzilla.proxmox.com/show_bug.cgi?id=5035#c2

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 recreate. you could have that included into your...

>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 two orders of magnitude more frequent in terms of...

yes, you are right, chances ar low, but i'm not not sure if we should really call it "over engineered" to check boot env for disk issues and to have "zfs|btrfs scrub" equivalent for bootenv. for all those who worry, here are some ideas how check could be done proactively: 1. patrol read of all...

yes, but while zfs is getting regular scrub, silent bitrot could indeed happen on partition1+2 on system which is rarely getting touched/updated. such issue will hit you when you don't expect it. chances are low indeed, but the sectors of partition1+2 don't get regular check and this is...

good and valid point. would you like to open a bugticket for this @emunt6 ?

this is also affected. https://bugzilla.kernel.org/show_bug.cgi?id=99171#c24

it seems newly created qcow2 on lvm do not initialize the storage with zero but assume the storage is all zero. so you provide the same data to the qcow2 on re-adding which was there before. try deleting the windows vm and before recreating create any tiny little vm on the same storage and...

clearing nvram via setting jumper on mainboard also solved this problem for me on dell r620

ouch. Wow, what a great writeup !!! thanks for making/sharing it ! will re-read tomorrow in depth.

>So with a local ZFS, and VM RAW disks, you can make use of the native ZFS snapshot feature. Which is (unlike QCOW I believe) instant. yes, but without fs-freeze from the guest agent and thus most likely having worse consistency