Fixes #6285 [0]. This also came up quite a few times already in the forum, most recently [1] (german).
Since we do expose the option in the UI for all products nowadays (on ZFS-on-root installations only tho), just always write to /etc/modprobe.d/zfs.conf. [0] https://bugzilla.proxmox.com/show_bug.cgi?id=6285 [1] https://forum.proxmox.com/threads/ram-auslastung-nimmt-%C3%BCber-die-zeit-drastisch-zu.164527/#post-760989 Testing ======= Tested for each product PVE, PBS, PMG the following - install on ZFS, not touching the ARC size setting - install on ZFS, set some explicit value for ARC size - installing on non-ZFS such as ext4 .. and checking afterwards that /etc/modprobe.d/zfs.conf was written and contained respectively - the default value for the product - the set value - again the default value for the product Also tested each case with the auto-installer for PVE and PMG. Diffstat ======== Christoph Heiss (3): run env: always return proper value for default zfs max arc size tui: bootdisk: always return proper value for default zfs max arc size fix #6285: install: always set up zfs modprobe configuration Proxmox/Install.pm | 11 +++--- Proxmox/Install/RunEnv.pm | 9 +++-- proxmox-tui-installer/src/views/bootdisk.rs | 32 +++++++++------- test/zfs-arc-max.pl | 42 +++++++++++++-------- 4 files changed, 57 insertions(+), 37 deletions(-) -- 2.48.1 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
