Search results

  1. S

    ZFS slow after upgrade to 2.2.0 in latest Proxmox Update

    Hi all, in the past we had some problems with the performance of ZFS slowing down after a few minutes, after a long ride, we decided to turn off the sync-Feature in our pool and that solved the problem for a long time. After the last upgrade of proxmox and ZFS 2.2.0, exactly the same problem...
  2. S

    Dataset cannot be destroyed with error "dataset already exists"

    Hi all, after a bad sync with zfs-autobackup I cannot delete 2 ZFS-datasets on my server. There are no snapshots or clones existing for these datasets, but it still shows USEDCHILD-space, and I'm wondering why. I'm able to rename the datasets. I can snapshot these 2 datasets too, and I can...
  3. S

    Cannot destroy dataset xxx: dataset already exists

    Hallo zusammen, nach einem mißglückten Sync mit zfs-autobackup kann ich auf meinem Target-Server die ZFS-Datasets nicht löschen. Das merkwürdigste daran ist, dass ich vorher alle Snapshots der Datasets gelöscht habe, aber trotzdem bei USEDCHILD Daten angezeigt werden, obwohl keine Children...
  4. S

    Storage replication notification mail for every SUCCESS also possible?

    Hi all, is there an easy way to trigger the replication to send an info mail also after a successful replication? I receive notifications in the case of failure at the moment, but I would like to change it in a way like it's possible in the backup jobs to "always notify". I need that for...
  5. S

    Nice little sh-script to monitor LVM-thin space with warn mail

    With these little 2 scripts you can monitor your LVM-thin space to be aware of snapshots killing your overprovisioned storage. Save each script as .sh-File, chmod +x the file and it's directly ready to use after finding the attribute output in LVS command. Change the mail-adress, it runs fine...
  6. S

    Win2019 Server PCie passthrough boot problems since last Proxmox update to 7.2 - \boot\bcd 0xc00000e9

    Hi all, since the last Proxmox Updates we had problems with a Win2019 Server using an Intel Optane PCIe-passthrough-device as boot volume. First we thought, it was an Windows-Update-Error, but it's not. A fresh install on a new VM of Win2019 Server runs normal till it reboots. The reboot ends...
  7. S

    Problems with replication since the last proxmox VE 7.1 update

    Hi all, I've big problems on replication of all vms since the last proxmox update. I've deleted all replication schedules and the replicated volumes. My ZFS pool is not on heavy load, all time between 0 and 10%, but no replication is ending successfully. Another question is, why are the...
  8. S

    General volume discard-question

    Mahlzeit zusammen ;) Mal eine generelle Frage: Discard auf einem Proxmox-VM-Volume ist zwar eine tolle Sache um den ZFS-Speicherplatz exakt auf die verbrauchten Daten einzugrenzen, aber kann es sein, dass es auf dem Boot-Volume von bspw. Winserver 2019 aufgrund der generellen Auslagerung von...
  9. S

    [SOLVED] ZFS Verhalten bei Windows-Volume verschlüsselt mit Bitlocker

    Auf einer Winserver 2019 VM gibt es ein Datenvolume mit exakt 1 TB Speicher. Auf dem ZFS Pool war vorher die Standard-Komprimierung an. Unnütz, wenn ich Bitlocker nutze innerhalb Windows, aber das sollte nicht das Problem sein. Wenn ich nun auf dem Windows-Volume die Verschlüsselung starte...

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!