惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

GbyAI
GbyAI
WordPress大学
WordPress大学
D
DataBreaches.Net
腾讯CDC
小众软件
小众软件
B
Blog RSS Feed
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
T
The Blog of Author Tim Ferriss
MongoDB | Blog
MongoDB | Blog
U
Unit 42
Y
Y Combinator Blog
V
V2EX
I
InfoQ
D
Docker
量子位
N
Netflix TechBlog - Medium
Recent Announcements
Recent Announcements
A
About on SuperTechFans
博客园 - 叶小钗
大猫的无限游戏
大猫的无限游戏
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
B
Blog
阮一峰的网络日志
阮一峰的网络日志
MyScale Blog
MyScale Blog

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
MEMDB_MAX_FILE_SIZE on pmxcfs is too small (1 MiB)
invalid@exam · 2026-06-22 · via Proxmox Support Forum

Hello everyone,
here I get that the value of the MEMDB_MAX_FILE_SIZE variable in memdb.h is too small, the impact is that when the /etc/pve/user.cfg file exceeds 1MB it cannot create any more users. Are there any suggestions to improve this?

I tried editing the max value of the variable, but it was very difficult, there were lots of errors in the proxmox service.

root@Research-Proxmox02:~# systemctl | grep pve | grep failed
● pve-firewall.service loaded failed failed Proxmox VE firewall
● pve-guests.service loaded failed failed PVE guests
● pve-ha-crm.service loaded failed failed PVE Cluster HA Resource Manager Daemon
● pve-ha-lrm.service loaded failed failed PVE Local HA Resource Manager Daemon
● pvescheduler.service loaded failed failed Proxmox VE scheduler
● pvestatd.service loaded failed failed PVE Status Daemon
root@Research-Proxmox02:~#

hd--

Proxmox Staff Member

Hello
The value of the variable and also the maxsize of the pmxfs are due to the fact that the entire pmxfs is stored in memory and is also synchronized in real time on all computers in the cluster.
I don't think that manually changing the value is a good option (You can run into a lot of problems, not least synchronization problems, which can be difficult to debug)
Hence, the question how many users do you require and is there the possibility to require less ?

[1] https://pve.proxmox.com/wiki/Proxmox_Cluster_File_System_(pmxcfs)

1MB seems very excessive.. could you describe your setup?

Hello
The value of the variable and also the maxsize of the pmxfs are due to the fact that the entire pmxfs is stored in memory and is also synchronized in real time on all computers in the cluster.
I don't think that manually changing the value is a good option (You can run into a lot of problems, not least synchronization problems, which can be difficult to debug)
Hence, the question how many users do you require and is there the possibility to require less ?

[1] https://pve.proxmox.com/wiki/Proxmox_Cluster_File_System_(pmxcfs)

maybe just in case the maximum number of users is 6000 and does not include ACLs in the user.cfg file, and maybe the size of the user.cfg file will continue to grow.

1MB seems very excessive.. could you describe your setup?

I'm using 20 hosts here and using Ceph as storage, do you have any suggestions?

no, I mean, what are you putting into user.cfg that you run into this limit? it's a plain text file, it only contains the user/permission related settings..

no, I mean, what are you putting into user.cfg that you run into this limit? it's a plain text file, it only contains the user/permission related settings..

sorry, I misunderstood, as you said the user.cfg file contains users, permissions, etc.

I put into user.cfg is user, token, ACL. And it will always increase the file size.

sorry, I misunderstood, as you said the user.cfg file contains users, permissions, etc.

I put into user.cfg is user, token, ACL. And it will always increase the file size.

How many lines are in there?

exactly, that is my question - what is your setup like that you need so many (or, alternatively, so big, if that is the case ;)) entries in user.cfg?

hello, I have made improvements to this case, there are 2 options:
1. You can hardcode edits on pve-cluster.
2. You can clean up resources on user.cfg that are not used.

1MB seems very excessive.. could you describe your setup?

I understand this sort of back-at-you question, but holistically, why not let user set it (hence also the pmxcfs limit as well) to whatever they want? Clearly there's enough space in RAM nowadays, so the only concern might be the syncing over network. I would rather wonder if files can't by synced as "diffs" rather than full refresh to minimize the traffic.

because then people would start to abuse /etc/pve as a shared storage like thing, which it is not. it's meant to sync small files that need to be available and consistent in a cluster. we have bumped the limits where sensible in the past, but we can only do so while keeping performance and failure conditions in mind.

Hi Proxmox Team,

I would like to follow up on this topic again after some time.

I understand the previous concern that /etc/pve should not be used as a shared storage-like location, and I agree with that.

However, in this case, the user.cfg growth comes from normal Proxmox access management data, such as users, API tokens, ACLs, and permission entries, not from unrelated files stored in pmxcfs.

I still think this case is worth reconsidering, since reaching the current limit can block the creation of additional users, tokens, or ACL entries.

Could this limitation be reconsidered in the future?