Recent content by fiveangle

Added my $0.02 on the ticket too. Bummer.

I think it's clear what we are looking for. How would we as a community effectively communicate this desire to the Proxmox team? Nodes have very specific changes from base installation for many HW configs so rather than having to continually update/test an Ansible playbook, a simple...

Ah, that’s a great test feature I haven’t seen before (and searching seems to back up that it’s not super common knowledge). Thanks. When I was testing HW NVMe RAID0 on a single-cpu Bronze X11 system, we had to drop a second cpu in just to saturate the card (9460-16i) with 12x P4500 4TB on the...

It's a wonder what either of you is talking about, because the ARC is integral to ZFS and cannot be "removed", only adjusted in size.

Can you please explain how the change helps to make Proxmox not run the processor at max frequency ? @spirit stated the change is to "force max frequencies" (which is exactly opposite of what this thread is about).

This is the default behavior in Proxmox and this thread is about disabling this behavior so I'm not sure how your comment adds to the discussion at all. Am I missing something ?

I find this ghost lock happens most often because of stale devicemapper handles. Not sure why it happens but it only seems to ever happen with Proxmox, so I suspect some cleanup from GUI operations not happening when it should. If you get this error, check the device mapper table for ghost...

I doubt there is anyway to “force” the p_state driver if the default kernel doesn’t enable it directly. I can’t seem to get it enabled on my old T110 ii with “supported” E31230 Sandybridge. I suspect it is due to the ancient Dell firmware not fully supporting them, even though the proc does.

From reviewing the docker ZFS driver detail documentation (https://docs.docker.com/storage/storagedriver/zfs-driver/) it seemed clear from the error that docker was not using the ZFS driver for /var/lib/docker when being nested on a ZFS-backed LXC as it should be. As a work around we force...

Just found same... So sad... okay, back to the dark ages of LVM from ZFS *sigh* -=dave

If by "let the CPU do the rest" you mean, let the CPU do nothing but run at it's lowest supported frequency, sure, but you're neutering performance, especially if you have a higher-end CPU that supports large CPU scaling factors...

Update: In addition to procedure to disable IPV6 on host, any LXC containers set to use DHCP for IPV6 on their network interface must be changed to STATIC and CIDR of default "NONE", else the LXC will continue to use IPV6. This seems like a bug to me, since there is no IPV6 DHCP server to...

FYI: Unfortunately, disabling via the proscribed method doesn't disable it in LXC containers that existed prior to when ipv6 was disabled via sysctl on the proxmox host... -Proxmox host set to static IPV4 address via netplan -Moved Proxmox host from network that supported DHCP ipv6 to network...

A standard stand-alone computer. Your problem is either 1) issues with the OS configuration (which might be better served at a forum dedicated to the distro you're using, or 2) networking issues within Proxmox (which would be prime to ask about here). Assuming your issue isn't #1, first...

yes, it should work as if they are normal systems