You mean has Broadcom RAID controllers that have issues with kernel 7 when instead of using a hw-raidset doing zfs on the disks behind - that's quiet a difference.
Jup. Und das läuft auch auf einem 08/15-PC problemlos deutlich länger als 100 Tage, wahrscheinlich sogar jahrelang. Vorausgesetzt natürlich, der PC raucht nicht irgendwann ab. Ist ja schließlich Linux und nicht Windows, das man einmal pro Woche...
WENN man gute Hardware hat (!) UND man Updates nicht zwingend installieren muss/will, DANN sind ein paar hundert Tage Uptime gar kein Problem.
Willkommen in der Linux Welt ;)
This is great ! I have been looking for a way to manage my ZFS datasets in an LXC without bloating the proxmox host with additional packages!
I have slightly altered/limited the mountpoints
arch: arm64
hostname: AlpineZFSmanager
memory: 512...
Proxmox is not intended to do that, as an clustered enterprise hypervisor. Maybe using Debian with KVM/QEMU directly or libvirt to create a VM with the same specs (except for memory, as Linux also needs memory) as that gives your more detailed...
Jup. Und das läuft auch auf einem 08/15-PC problemlos deutlich länger als 100 Tage, wahrscheinlich sogar jahrelang. Vorausgesetzt natürlich, der PC raucht nicht irgendwann ab. Ist ja schließlich Linux und nicht Windows, das man einmal pro Woche...
I'll drop this here: https://pve.proxmox.com/wiki/Multipath
We are currently also working on getting iSCSI, LUN and multipathing integrated into the Proxmox VE tools and web UI. So keep an eye out for it in future release notes.
What do you mean by the same settings?
The same amount of CPU cores, sure. Same amount of memory: no, the hypervisor requires a couple of gigabytes as well. CPU feature flags: yes, set it to type host.
$(pwd) resolves to the current directory/path you're in. pwd tells you where that is.
I felt like that is the easiest way to give you something that definitely works. No need to make this complicated by involving weird paths.
Thanks for the insight.
I did manage to find the following explanations:
Metric NameMeaning
`proxmox_node_uptime_seconds`
Host uptime in seconds.
`proxmox_node_cpustat_cpu_percent`
Current node CPU usage percentage...
I'll drop this here: https://pve.proxmox.com/wiki/Multipath
We are currently also working on getting iSCSI, LUN and multipathing integrated into the Proxmox VE tools and web UI. So keep an eye out for it in future release notes.
Ceph is RAM hungry, not really great at high ram cost right now. As we are lucky and have enough ram(still) we are using 2gb per 1tb of NVMe storage.
The default setting in Proxmox is 2GB(flat) and that is waaaay too low for large NVMe disks...
Are you using Ceph 20.2.x as EC got major improvement with 20.2.x ?
If you are mixing drives, expect the storage to be as "fast" as the slowest disk.
Maybe instead of mixing disks you could create different pools with different crush rules...
Running ZFS on a obfuscated device (eg, RAID LUN) isnt dangerous per se; its no safer then any other filesystem on raid- which is to say you have no checksum correction facility at the filesystem level so you're paying the zfs tax for no gain...
Well, https://pve.proxmox.com/pve-docs/chapter-pvesm.html#_storage_types lists it explicitly as "ZFS (local)"!
ZFS wants to have direct access to the hardware of the devices. This has been discussed multiple times for "pass-through disks or a...
the advanced idea is to have 2 (Storage) VMs in a HA pacemaker cluster running under Proxmox VE .... each of the VM has access to SAN LUNs which host one or more zpools which can failover to the other VM .... the zpools are then exposed via...
Ich will ja hoffen,das wir uns das thema hier nicht noch weitere 18 Monate antun müssen. Ich kann beim besten Willen hier überhaupt nicht erkennen, was das Ganze mit Proxmox zu tun hat. Technische Probleme gibt es bei der Nutzung jedenfalls...