mirror of
https://github.com/jiangcuo/zfsonlinux.git
synced 2025-08-26 16:58:55 +00:00
595cc7bfa1
the following patch seems applicable and might fix an issue observed in our enterprise support a while ago. containers run in their own cgroups, thus were probably not scanned by the kernel shrinker - this resulted in Dnode cache numbers of 300+% reported in arc_summary. FWICT the issue was introduced in ZFS 2.2.7 (commit 5f73630e9cbea5efa23d16809f06e0d08523b241 see: https://github.com/openzfs/zfs/issues/17052#issuecomment-3065907783) but I assume that the increase of zfs_arc_max by default makes it trigger OOMs far easier. The discussion of the PR was quite instructive: https://github.com/openzfs/zfs/pull/17542 minimally tested on a pair of trixie VMs (building + running replication of a couple of containers) Suggested-by: Thomas Lamprecht <t.lamprecht@proxmox.com> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com> Link: https://lore.proxmox.com/20250723181453.1082366-1-s.ivanov@proxmox.com |
||
|---|---|---|
| .. | ||
| 0001-Check-for-META-and-DCH-consistency-in-autoconf.patch | ||
| 0002-always-load-ZFS-module-on-boot.patch | ||
| 0003-Fix-the-path-to-the-zed-binary-on-the-systemd-unit.patch | ||
| 0004-import-with-d-dev-disk-by-id-in-scan-service.patch | ||
| 0005-Enable-zed-emails.patch | ||
| 0006-dont-symlink-zed-scripts.patch | ||
| 0007-Add-systemd-unit-for-importing-specific-pools.patch | ||
| 0008-Patch-move-manpage-arcstat-1-to-arcstat-8.patch | ||
| 0009-zpool-status-tighten-bounds-for-noalloc-stat-availab.patch | ||
| 0010-enforce-arc_dnode_limit.patch | ||
| series | ||