Wow, this hit me hard, too. Had this on my offsite ZFS backup, where I received ZFS datasets/snapshots with Syncoid. This was really tricky to identify, thank you for reporting!
Thank you. I think I tend to do the following:
- keep automated, full snapshots using the PVE snapshot utility (will create tar's of VMs/LXC etc., properly suspend guests etc.)
- install Sanoid on Proxmox itself, create automated inexpensive ZFS snapshots of all datasets, including VM disks but...
Did you every find an answer to this? I am at the same stage, trying to setup sanoid in a privileged LXC on Proxmox, to not dirty the Hypervisor. I have set up Syncoid in Pull mode, with a specific user on the Hypervisor that is limited in rights using ssh command restrictions, so I am only...
Just updated to 8.0.3 and everything went smooth on my single-node, 20x LXC, nested Docker, zfs-backed Proxmox! All services ran immediately as if nothing happened.
I'll need to look into this more closely, but it follows what I described here
https://du.nkel.dev/blog/2021-03-25_proxmox_docker/
.. and it has worked flawlessly since 3 years, tested up till the current Proxmox 7.3-4.
The latter steps look like this is solving the migration issue, thanks for...
> warum um alles in der welt will man docker in lxc containern laufen haben, wenn es dauernd bei updates kaputt geht und "strongly discouraged" ist ?
Da gibt es mehrere, jeder muss selbst entscheiden:
1. Ressourcen: Ich habe bei mir nur 32GB RAM ohne Möglichkeit auf zeitnahes (< 2 Jahre)...
I like the basic approach from Proxmox. You can extend sensor collection yourself, just set up Telegraf & InfluxDB, e.g. Proxmox Hypervisor Monitoring with Telegraf and InfluxDB.
Great, thank you. Very informative. My server is only available locally/IPsec/vpn, Services are further separated in several VLANS and firewalled in a Demilitarized Zone (only response allowed). Otherwise, I would also prefer VMs.
Yes, I think I monitor host bytes, the Evo attribute is called "Total_LBAs_Written" and the WD reports "Host_Writes_GiB". Most of my DBs do 90% read and only rarely write, so this makes sense. I also have encryption+compression enabled on all my pools. Interesting..
Really? I wonder what you do. I have two extra boxes for OPNsense and pfSense, apart from that, everything runs on my Proxmox:
- Gitlab (~100 Repositories currently)
- Nextcloud (9TB of data, the data folder is mounted from a spinning rust ZFS pool)
- Funkwhale
- Iris/Mopidy/Snapcast
-...
My 5 cents about write intensity with ZFS/SSD:
I have 2x "Consumer" Western Digital SSDs (2x WDC WDS500G1R0A-68A4W0) as my "VM" ZFS Mirror Pool (about 20 Services, 11 Users, about 11 Postgres/MySQL databases), the total accumulated TBW over 1 year is 33.57, which was what I calculated ahead of...
I use an Odroid Cloudshell 2 with 2x 16 TB HDDs in Raid, offsite. Once weekly, Proxmox connects via IPSEC, boots the Odroid, syncs data with rsync and borgmatic, and shuts down the Odroid afterwards.
Doesn't help me with the HDD costs, but keeps energy low and it is a pretty flexible setup.
Here's the "report":
https://du.nkel.dev/blog/2022-01-21_proxmox_root_migration/
I am not sure how much value is added with this, because setups may highly vary, but maybe this can serve as a starting point. Let me know if you see anything that should be changed.
Many thanks for the explanations. I want to ask and verify if I understood correctly: The ZFS bug with swap only applies in situations with low space? I have a dedicated ZFS Mirror for rpool with 250GB, and since Proxmox only consumes 5GB, I have 230GB available. That means having 8GB swap on...
I don't - I haven't had the need for shared bind mounts. Have you enabled fuse in the Container Proxmox options (under Features)? The link you gave refers to virtual fuse mounts produced inside the container, linked back to the host. If it is an issue, I think this may not have something to do...
> Sorry, but using XFS ontop of ZFS is not using ZFS. You also did not go to another continent by bicycle if you're sitting on it while flying on a plane.
I quote myself:
> but it is on lower-end-machines significantly slower than using ZFS directly on the host.
I have done extensive...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.