Recent content by UdoB

Are you sure you know exactly what this does? I am sure, I do not ;-) My recommendation: return to a default setup, then it will react with the default behavior.

One very low-end approach, with these assumptions: you have two nearly identical PVE server, not clustered one is doing its job, the other is turned off you have sane PBS (with SSDs only, at least for the latest backup) - as you need to have daily backups anyway, right? When the primary...

The very clear and ultimate answer is of course: it depends! If you have enough experience to administrate a Debian server consistently and continuously over years, including disaster recovery, then you may go that route. (And use a single server instead of a cluster.) If the loss of the...

You might produce something like "FABC: optimizing a pool by utilizing the new features of ZFS 2.4" or similar ;-) I would definitely read it :-) I hesitate to roll out that update (in my Homelab) though...

2.4 seems to be in non-sub now: Get:1 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 zfs-initramfs all 2.4.0-pve1 [26.3 kB] Get:2 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 libnvpair3linux amd64 2.4.0-pve1 [50.1 kB] Get:3...

Assuming HDDs: You mentioned Raid6. This gives you the IOPS of a single disk. A verify need to read the actual data, calculate the checksum and compare it with the stored original checksum. There is no single, large file to be read. Instead it needs to read some ten thousands of chunks, possibly...

First compare your expectations with this one: https://wintelguy.com/zfs-calc.pl For 6 * 8000 GB it gives 43.655746 TiB raw - which is shown in the second screenshot of #3. The construction of your single vdev worked as expected. Check zpool get all S and zfs get all S to verify there are no...

The relevant parameter seems to be VolBlocksize: https://forum.proxmox.com/threads/zfs-metadata-special-device.129031/post-564817

Sounds good. So..., what is your problem? Please report a) what you wanted to achieve, b) exactly what you did, c) what you expected to happen and d) what happened instead. If possible do everything on the command line and place full quotes (including the full command and the full error...

Your "+1" is probably better placed over there: https://bugzilla.proxmox.com/show_bug.cgi?id=6144, already mentioned in #47. You'll also find a patch already mentioned in the last comment.

That's what backups are for ;-) Snapshots do not count for that. Be it LVM or ZFS or QCOW or xyz... ---- Edit, not mentioned yet: when I do delete a VM I want to be sure that all data is actually gone! If there are rudiments left over then the mechanism is defect!

Ja, genau. Ich nehme einen meiner externen Emailprovider und lasse alle Email dort relayen. Anleitungen dazu gibt es zuhauf, eine konkrete kann ich - ohne selber zu suchen - aber nicht nennen. Postfix ist ein ausgewachsenes Mailsystem...

That's interesting as PVE uses an Ubuntu Kernel ;-) Possible workaround as a last resort: install Debian Trixie first, then install PVE - https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_13_Trixie - you would lose "OS on ZFS" though...

sendmail gehört (per Default) zu Postfix: ~# dpkg -S $(which sendmail) postfix: /usr/sbin/sendmail Wie sendmail mit dem eigentlichen Postfix kommuniziert ist mir gerade unklar - und egal ;-) Wichtig ist, dass diese Konstruktion nur dann korrekt funktioniert, wenn sie vollständig konfiguriert...

You have pools with different names. (( And this prevents replication which is really annoying :-( )) Migration of running VMs allows me to select a specific storage on the target Migration of LXC does not offer this to me At the end... backup/restore should work. There is no easy...